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