[
https://issues.jboss.org/browse/SHRINKWRAP-325?page=com.atlassian.jira.pl...
]
Aslak Knutsen commented on SHRINKWRAP-325:
------------------------------------------
Arquillian and Shrinkwrap will be added, which is normal because
their classes are used in our test classes (@Arquillian, ShrinkWrap.create...) at test
runtime.
Arquillian has it's own way of packaging it self that it does runtime. It's not
the same version / configuration that runs incontainer as you have on your client cp.
Adding Arq as the Client v most likely fail
Maven based shrinkwrap WebArchive creator that adds all WEB-INF
descriptors, classes, test classes and webapp resources too (not just dependencies and
test dependencies)
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: SHRINKWRAP-325
URL:
https://issues.jboss.org/browse/SHRINKWRAP-325
Project: ShrinkWrap
Issue Type: Feature Request
Reporter: Geoffrey De Smet
Priority: Critical
The MavenDependencyResolver is nice, but it does only half the job.
We still have to manually add "target/guvnor-webapp-5.3.0-SNAPSHOT/"
or "target/classes" and "target/test-classes" and
"src/webapp/WEB-INF/*" files etc.
But all that info is in the pom model, so it would be nice to have a feature as a facade
for that.
Something like
{code}
ShrinkWrap.createEntirelyFromMavenPom("pom.xml", includeEntireTestClasspath).
{code}
Note that it can include the entire test classpath (for helper classes under
"target/test-classes" and dependencies such as Mockito).
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira