-
1. Re: Parse dependendencies from maven pom
meetoblivion Apr 6, 2010 7:24 AM (in response to kenglxn)why skip the test scope?
-
2. Re: Parse dependendencies from maven pom
kenglxn Apr 6, 2010 7:28 AM (in response to meetoblivion)Initially i just thought we wouldn't want to deploy junit/testng jar etc.
-
3. Re: Parse dependendencies from maven pom
aslak Apr 6, 2010 7:34 AM (in response to kenglxn)This seems to be close to the discussion in this thread: http://community.jboss.org/message/523810#523810
-
4. Re: Parse dependendencies from maven pom
kenglxn Apr 6, 2010 7:43 AM (in response to aslak)Very nice. Didn't see that before.
I like the
archive.addLibrary(Maven.library("groupid", "artifactid", "version"))
Would be nice to select all the dependencies that are a part of the projects pom(s).
e.g:
archive.addLibrary(Maven.currentProjectDependencies())
This might avoid false positives if there is some sort of dependency problem.
I'm thinking in particular to cases where an integration test might go green, but when project is built with maven and shipped out, there is an additional jar that was not there in the arquillian integration test that causes problems.