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
What are your thoughts on adding an evaluation step?
The aim is to walk the transitive dependency graph for all of the maven resources and present a new build file on stdout.
For diamond dependencies that have incompatible versions it would create one line per version.
The evaluated file would be sorted with comments stripped.
Only compile time scope would be followed.
Scenario
Given a build.dependencies file that contains a.A@1.0
And a.A@1.0 depends on b.B@1.0 and c.C@1.0
And b.B@1.0 depends on d.D@1.0
And c.C@1.0 depends on d.D@1.1
When the file is evaluated
Then stdout should contain the following:
```
mvn:a:A:jar:1.0
mvn:b:B:jar:1.0
mvn:c:C:jar:1.0
mvn:d:D:jar:1.0
mvn:d:D:jar:1.1
```
The text was updated successfully, but these errors were encountered:
What are your thoughts on adding an evaluation step?
The aim is to walk the transitive dependency graph for all of the maven resources and present a new build file on stdout.
For diamond dependencies that have incompatible versions it would create one line per version.
The evaluated file would be sorted with comments stripped.
Only compile time scope would be followed.
Scenario
The text was updated successfully, but these errors were encountered: