I don't believe wrong is the correct term to describe the situation, rather, 
from your (Seam team) perspective, you provide examples that are based on 
'things' being in places in the Seam 2.0.0.CR(X) distribution.  Thus, jars like 
"jboss-embedded-all.jar" are not truly all.  I say that because I had to 
discover (the hard way) that I needed to add jboss-embedded-api.jar and 
jboss-deployers.jar to my repo and test-scoped dependencies to my pom.xml.  No, 
this is not in the Seam 2.0.0.CR3 docs - I double checked.  I'm guessing your 
ant scripts build up classpaths using the lib and the lib/test directories in 
the distro and so it's easy to miss this kind of thing.  I also just discovered 
that I need to add hibernate-commons-annotations.jar to my test-scoped 
dependencies, and thus, again, hibernate-all.jar is not truly all.  It would be 
nice if the 'all' jars were truly 'all'. ;-)

I also needed to learn the jboss embedded container layout a bit;  this is so 
that I could put appropriate maven2 testResource instructions into my pom(s) 
and reproduce the bootstrap directory layout.  And... I needed to figure out 
that I need to copy my target/classes contents to the bootstrap deploy dir (I 
haven't figured out how to get the bootstrap to treat target/classes as part of 
the classpath).  I'm close now.

Thanks,
Brad

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100368#4100368

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100368
_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to