Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First implementation of an automatically generated Gradle platform from the SciJava Pom
The current version is based on the latest 38.0.0-SNAPSHOT
I added a commented line which will return all the dependencies constraints for the selected configuration (related)
Note, you can do that only for the configurations which has
isCanBeResolved == true
, "compileClasspath" is one of these.Unfortunately, it looks like you cant retrieve out-of-the-box all the dependencies constrains brought in by the platform, but you can loop all the dependencies constrains which come into play in the project dependency resolution
I said out-of-the-box, because we can always parse the platform
.module
file and retrieve them ourselvesThis PR servers as an hook to play around this first platform implementation
At the moment, the platform has
0.1
, but in the future it will probably be in sync with the upstream Scijava-pom