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 d77a2ef
Browse filesBrowse the repository at this point in the historyBrowse files
fix(manifest): keep the paths of a module excluded with --exclude-paths
An excluded module emitted no project record, so its sources and
classpath vanished from the sidecar and the kept projects depending on
it were analysed without its code. The Maven, Gradle and sbt producers
now emit an excludedProject record for it under --with-files: it gets
no project of its own, but its paths stay.
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
@@ -19,6 +19,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
19
19
- Gradle dependencies that fail dependency verification, or whose jars cannot be fetched, are reported instead of passed on as healthy.
20
20
- Failed Gradle project dependencies are reported instead of silently dropping everything they pull in, and failures name the version that actually failed.
21
21
- sbt dependencies whose jars coursier skips or Ivy fails to download are reported instead of passed off as POM-only modules, and POM-only, war and aar modules keep their real shape.
22
+
- A module excluded with `--exclude-paths` is still analysed as part of the projects that depend on it.
Copy file name to clipboardExpand all lines: src/commands/manifest/scripts/maven-extension/src/main/java/tech/coana/socket/SocketFactsRecordsEngine.java
0 commit comments