-
1. Re: Arquillian missing dependency?
aslak Mar 1, 2012 5:43 PM (in response to rcd)https://community.jboss.org/message/633954
https://community.jboss.org/thread/165840
Basically there is something wrong with this lib org.jboss.spec:jboss-javaee-web-6.0:2.0.0.Final
-
2. Re: Arquillian missing dependency?
rcd Mar 2, 2012 9:55 AM (in response to aslak)I'm importing org.jboss.spec:jboss-javaee-6.0:3.0.0.Beta1. Xalan is part of that artifact's dependency tree, but I'm importing it with provided scope seeing as the JBoss server provides those libraries. Hence it's not on the classpath when Jenkins tries to initialize the tests since they're not initialized in the container and Maven isn't adding them. I guess the solution is to just add Xalan to the POM with test scope.
-
3. Re: Arquillian missing dependency?
aslak Mar 2, 2012 5:38 PM (in response to rcd)But you're defining the javaee lib in the same module that has the tests right? provided is only relevant for modules that depend on you, not within the module it self.
-
4. Re: Arquillian missing dependency?
rcd Mar 5, 2012 10:09 AM (in response to aslak)According to the Maven documentation, dependencies with provided scope are included on the compile and test classpaths, but not on the runtime classpath. This includes all transitive dependencies of a provided-scope dependency, so org.apache.xalan:xalan:2.7.1-1.jbossorg IS on the classpath. The dependency that's missing is actually org.apache.xalan:serializer:2.7.1-1.jbossorg.