Compile-Time API Leak to SWD

[alrubinger]

We have a compilation-time API leak from Arquillian Core to SWD:

Description	Resource	Path	Location	Type
The type org.jboss.shrinkwrap.descriptor.api.Descriptor cannot be resolved. It is indirectly referenced from required .class files	VertxCommonDeployableContainer.java	/vert.x/src/main/java/org/vertx/java/arquillian/container	line 1	Java Problem

Stumbled across this while implementing a DeployableContainer for the VertX project tonight.

While it's one thing to require SWD for Arquillian to run internally, it's another to impose any specific version for compilation.  What can we do to isolate this?

S,

ALR

[aslak]

How is this any different then Archives ?

What is your pom setup?

[alrubinger]

Archives?  It's different because ... why would a user need SWD on the compilation ClassPath in order to implement a DeployableContainer?

Ha, no POM setup.  Tim's used Ant for the Vert.X build.  Which actually makes me think we should start making unified distribution JAR assemblies to bundle all of our modules together (kinda like putting all the contents of the depchain POMs in one JAR).  WDYT?  If so I'll open a new discussion for this.

S,

ALR

[aslak]

Archives are not different in this context.

Descriptors are defined as a 'Deployable Unit' on the same level as Arcihves.

shrinkwrap-api and shrinkwrap-descriptor-api are required.

[alrubinger]

Ah, that's right, Descriptors are directly deployable.  OK, so that makes sense then, thanks.

Mental note: For ARQ 2.0.0, anything should be Deployable.   For instance in VertX it's just Classes.  And for some container types it's *nothing*.

S,

ALR

[aslak]

physical note... https://issues.jboss.org/browse/ARQ-473