My recommended simpler hack:
- Remove MavenArtifactResolver (we'll eventually plug in SHRINKWRAP-140)
- Put the JAR in src/test/resources
- Use that
This way we keep the build environment-independent. Aslak's plugging in a SW branch for proper, configurable Maven dep resolution.
thanks - the new MavenArtifactResolver does look very nice.
What's the reason for not adding it to Arquillian/ShrinkWrap API, already?
So, AFAIK https://jira.jboss.org/browse/ARQ-66 goes beyond that and is an arquillian issue.
Your MavenArtifactResolver would need to go into ShrinkWrap API - is that right?
Thanks and regards