Re: dependency:tree without downloading binaries
On Tue, May 30, 2017 at 5:25 PM, Viktor Sadovnikovwrote: > Hello everyone, > > I need to collect information about dependencies (their GAV only) of a very > large number of projects. Therefore I wrote a simple Maven plugin. It's is > based on maven-dependency-plugin, but reports dependencies in a format, > whihc I can use later. > > However applying this plugin to projects results in filling local maven > repository with binaries of all the dependencies with their different > versions. It's vey time consuming and hungry for the disk space. Is there a > way to make DependencyGraphBuilder (class from Maven Shared) to resolve > dependencies using poms only? wihtout downloading actuall binaries? > There is already an issue for that: https://issues.apache.org/jira/browse/MSHARED-519 Cheers Stefan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: DependencyTreeBuilder vs. DependencyGraphBuilder
I haven't had any problems so far. I was just confused by DependencyTreeBuilder's Javadoc. It says that (at least I understood it that way) the dependency graph might differ from the dependency resolution in Maven 3. The same Javadoc references an Issue (MSHARED-167) that was solved two years ago. So I was not sure if differences can still occur or not. According to Hervé's reply, differences can still occur. Cheers, Stefan On Wed, Apr 2, 2014 at 2:49 AM, Martin Gainty mgai...@hotmail.com wrote: Stefan A year ago..Herve says r1469697 maven-dependency-tree is fixed for M3 Is this not the case? Martin Date: Tue, 1 Apr 2014 08:29:20 +0200 Subject: DependencyTreeBuilder vs. DependencyGraphBuilder From: st.fer...@gmail.com To: users@maven.apache.org I'm using the org.apache.maven.shared:dependency-tree library to gather dependency information on my projects. In order to get additional information about version conflicts, I prefer to use DependencyTreeBuilder instead of DependencyGraphBuilder. However, the Javadoc of DependencyTreeBuilder says: Notice that it doesn't fail with Maven 3, but when Maven 2 and Maven 3 don't calculate the same transitive dependency result, the tree calculated with this component is consistent with Maven 2 even if run with Maven 3 (see MSHARED-167) The issue MSHARED-167 [1] was closed in June 2012. So may DependencyTreeBuilder still produce different results than DependencyGraphBuilder or is this not an issue anymore? Cheers, Stefan [1] https://jira.codehaus.org/browse/MSHARED-167 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
DependencyTreeBuilder vs. DependencyGraphBuilder
I'm using the org.apache.maven.shared:dependency-tree library to gather dependency information on my projects. In order to get additional information about version conflicts, I prefer to use DependencyTreeBuilder instead of DependencyGraphBuilder. However, the Javadoc of DependencyTreeBuilder says: Notice that it doesn't fail with Maven 3, but when Maven 2 and Maven 3 don't calculate the same transitive dependency result, the tree calculated with this component is consistent with Maven 2 even if run with Maven 3 (see MSHARED-167) The issue MSHARED-167 [1] was closed in June 2012. So may DependencyTreeBuilder still produce different results than DependencyGraphBuilder or is this not an issue anymore? Cheers, Stefan [1] https://jira.codehaus.org/browse/MSHARED-167 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org