Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Implemented
-
12.4, 12.5
Description
To reproduce: checkout the project git@github.com:micronaut-projects/micronaut-test.git and open its subproject test-bom
The project load reports broken dependencies for:
classpath +--- org.junit:junit-bom:5.7.1 -> 5.7.1 FAILED \--- org.spockframework:spock-bom:2.0-M3-groovy-3.0 -> 2.0-M3-groovy-3.0 FAILED
as well as gradle dependencies command. But the message is:
.... because no repositories are defined.
But the outermost project defines repositories block. gradle build in the -bom subproject succeeds - so perhaps it does not attempt to resolve the entries in the classpath configuration ?
The net effect is that the 'bom' project is always marked with a warning and 'resolve project problems' action does nothing. If a project's summary state is displayed i.e. in a LSP client, the project as a whole appears to be buggy (but it apparently is not).
lkishalmi could you please advise why Gradle is reporting 'no repositories defined' ? Or how to filter out this type of no-errors from the retrieved info maps ? Naturally I wouldn't like to suppress real resolution errors...
Attachments
Issue Links
- links to