You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 80e50d9
Browse filesBrowse the repository at this point in the historyBrowse files
fix(manifest): keep Maven dependencies left under a sibling's test-jar (#1684)
A module that reaches a sibling through both its jar and its test-jar
shares one node for both, but Maven can keep the sibling's dependencies
under the test-jar alone. The walk visited each node once, so it skipped
that subtree and the dependencies were missing from the SBOM. Key the
visited set by the full coordinate instead.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
12
12
### Fixed
13
13
-`--exclude-paths` patterns are now matched relative to the scan root in every build root. They now also exclude modules a build reaches outside its own directory (Maven `../` modules, relocated Gradle projects) and modules matched by wildcards that span a build-root boundary, such as `*/core`.
14
14
-`--exclude-paths` patterns written with Windows `\` separators now exclude JVM build modules in single-root runs too.
15
+
- Maven SBOMs keep the dependencies a module reaches through a sibling module's test-jar.
Copy file name to clipboardExpand all lines: src/commands/manifest/scripts/maven-extension/src/main/java/tech/coana/socket/SocketFactsRecordsEngine.java
0 commit comments