10:56 a.m.
Running a mvn dependency:analyze from the jbossas/thirdparty does not
produce any output:
[INFO] [dependency:analyze]
[INFO] Skipping pom project
Is there a way to get this info for a pom project?
2:12 p.m.
The dependency:analyze can't be used with thirdparty. For a normal
maven project, that goal compares what your classes are compiling
against with the dependencies of your project. But since the thirdparty
directory doesn't have any classes of it's own, maven doesn't have a way
to do this analysis.
Scott Stark wrote:
Running a mvn dependency:analyze from the jbossas/thirdparty does not
produce any output:
[INFO] [dependency:analyze]
[INFO] Skipping pom project
Is there a way to get this info for a pom project?
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
2:30 p.m.
That makes it painful to track duplicate dependencies. For example, I'm
trying to figure out everything include javax.xml.bind:jaxb-api right
now, and its too slow grepping the poms. What's the simplest change to
allow this to run?
Paul Gier wrote:
The dependency:analyze can't be used with thirdparty. For a
normal
maven project, that goal compares what your classes are compiling
against with the dependencies of your project. But since the
thirdparty directory doesn't have any classes of it's own, maven
doesn't have a way to do this analysis.
Scott Stark wrote:
> Running a mvn dependency:analyze from the jbossas/thirdparty does not
> produce any output:
>
> [INFO] [dependency:analyze]
> [INFO] Skipping pom project
>
> Is there a way to get this info for a pom project?
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
2:47 p.m.
I run mvn dependency:tree successfully on POMs which just specify
dependencies - this gives you a tree structure showing where
dependencies come from. You need to make sure you are using
org.apache.maven.plugins:maven-dependency-plugin:2.0
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.0</version>
</plugin>
</plugins>
</pluginManagement>
On 7 Aug 2008, at 20:30, Scott Stark wrote:
That makes it painful to track duplicate dependencies. For example,
I'm trying to figure out everything include javax.xml.bind:jaxb-api
right now, and its too slow grepping the poms. What's the simplest
change to allow this to run?
Paul Gier wrote:
> The dependency:analyze can't be used with thirdparty. For a normal
> maven project, that goal compares what your classes are compiling
> against with the dependencies of your project. But since the
> thirdparty directory doesn't have any classes of it's own, maven
> doesn't have a way to do this analysis.
>
> Scott Stark wrote:
>> Running a mvn dependency:analyze from the jbossas/thirdparty does
>> not produce any output:
>>
>> [INFO] [dependency:analyze]
>> [INFO] Skipping pom project
>>
>> Is there a way to get this info for a pom project?
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
9:02 p.m.
Thanks, that is working fine.
Pete Muir wrote:
I run mvn dependency:tree successfully on POMs which just specify
dependencies - this gives you a tree structure showing where
dependencies come from. You need to make sure you are using
org.apache.maven.plugins:maven-dependency-plugin:2.0
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.0</version>
</plugin>
</plugins>
</pluginManagement>
5978
days inactive
5979
days old
jboss-development@lists.jboss.org
4 comments
3 participants
participants (3)
-
Paul Gier -
Pete Muir -
Scott Stark