[
https://issues.apache.org/jira/browse/MSHARED-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358669#comment-17358669
]
Robert Scholte commented on MSHARED-788:
----------------------------------------
I don't think it is possible to build a project with cyclic (reactor)
dependencies. This seems to be a mistake in batik-poms. You cannot fix them in
your own pom and Aether already ensures it is not loaded twice, so that should
be fine.
The output related to premanaged versions and omitted for duplicate/version
difference look like fixes in the dependency tree (so these were actually bugs
in maven 2).
The additional dependencies for batik-script also looks correct to me.
So I think there is 1 thing that needs to be fixed:
{{org.apache.maven:maven-profile:jar:2.0.4:test (scope not updated to compile)}}
This looks like a warning where the scope has been reduced to test, whereas it
is likely required at runtime.
> Add functionality to collect raw dependencies in Maven 3+
> ---------------------------------------------------------
>
> Key: MSHARED-788
> URL: https://issues.apache.org/jira/browse/MSHARED-788
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-dependency-tree
> Affects Versions: maven-dependency-tree-3.0, maven-dependency-tree-3.0.1
> Reporter: Gabriel Belingueres
> Assignee: Robert Scholte
> Priority: Major
> Fix For: maven-dependency-tree-3.1.0
>
> Time Spent: 10m
>
> Add funcionality allowing to collect raw project dependencies. Add a layer to
> hide against Maven 3's sonatype aether and Maven 3.1+ eclipse aether.
> This could be used to implement dependencyConvergence and
> requireUpperBoundDeps enforcer rules.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
