Hi,
+1 for the idea of making a dependency:resolve-gui goal; it would be
nice :-)
I have a problem testing your tool : it doesn't seem to properly manage
properties.
I don't know if it comes from your code or maven-model but there's an
issue having in a pom.xml something like this :
...
<properties>
<module1.version>1.0-SNAPSHOT</module1.version>
</properties>
<modules>
<module>module1</module>
<module>module2</module>
</modules>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>group1</groupId>
<artifactId>module1</artifactId>
<version>${module1.version}</version>
</dependency>
</dependencies>
</dependencyManagement>
Both module1 and module2 use this pom as parent and module2 has module1
as a dependency.
I get the following error and, running it from eclipse, I can see the
tool finds two versions for module1 : "1.0-SNAPSHOT" and
"${module1.version}".
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
at java.io.File.<init>(File.java:277)
at
org.maven.dependencybrowser.implementations.local.LocalDiskRepository.resolveFile(LocalDiskRepository.java:29)
at
org.maven.dependencybrowser.controller.ArtifactResolver.resolveFile(ArtifactResolver.java:93)
at
org.maven.dependencybrowser.controller.ArtifactResolver.resolveArtifact(ArtifactResolver.java:64)
at
org.maven.dependencybrowser.controller.Controller.resolveArtifact(Controller.java:109)
at
org.maven.dependencybrowser.model.PomFile.resolveDependencies(PomFile.java:26)
at
org.maven.dependencybrowser.model.RootPom.resolveDependencies(RootPom.java:35)
at
org.maven.dependencybrowser.controller.Controller.loadPom(Controller.java:50)
at
org.maven.dependencybrowser.gui.DependencyBrowserGui$4.actionPerformed(DependencyBrowserGui.java:136)
...
I've tested on multiple projects (all defined in a similar way and got
the same result); of course, the projects I tested your tool on are
working with maven and most plugins.
Rune Flobakk a écrit :
I don't think there is anything stopping anyone to wrap a
plugin/MOJO-interface around the maven-dependency-browser to achieve
what you suggest :)
- Rune
Martin Gilday wrote:
Thanks Jake. I wasn't suggesting you move away from the GUI, I just
wasn't aware that you couldn't lauch a GUI from a Maven plugin. It
would just be nice for something like this to be part of the dependency
plugin. mvn dependency:resolve is great, mvn dependency:resolve-gui
would be even better.
----- Original message -----
From: "jake pezaro" <[EMAIL PROTECTED]>
To: [email protected]
Date: Sun, 25 Nov 2007 13:38:50 -0800 (PST)
Subject: Re: Dependency Browser Tool
there are a couple of reasons why this is not a maven plugin.
1. we found it much easier to understand the dependency tree when it
was
displayed in a GUI (ie being able open and close branches, see paths
being
highlighted etc). if this were to be a plugin it would need to display
text output, which we couldn't make as easy to understand (although if
you
have any ideas here then please send me an example).
2. maven reactor already provides a more static version of this
information
in it's convergence reports. we didn't want to replicate that
functionality, we just wanted a simple tool to track down rouge
transitive
dependencies.
Martin Gilday wrote:
Is there any reason this isn't a Maven plugin though? --repository
could
be taken from settings.xml
--workspace could just be the current directory where you run mvn
xx:xx.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
