[
https://jira.jboss.org/browse/ARQ-321?page=com.atlassian.jira.plugin.syst...
]
Dan Allen updated ARQ-321:
--------------------------
Summary: Test enrichers should provide a ready-made auxiliary archive dependency
(was: Test enrichers should provide a ready-made deployment appender dependency)
Test enrichers should provide a ready-made auxiliary archive
dependency
-----------------------------------------------------------------------
Key: ARQ-321
URL:
https://jira.jboss.org/browse/ARQ-321
Project: Arquillian
Issue Type: Feature Request
Components: Packaging Enricher SPI, Runtime Enricher SPI
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Priority: Minor
Fix For: 1.0.0.CR1
Each test enrichers implementation should provide a dependency that packages the test
enricher as an auxiliary archive. Currently, a container adapter will assemble an
auxiliary archive of the test enrichers that are supported by that container. But there
are cases when the container may have been enhanced with additional capabilities that
allow it to support an additional enricher. At this point, it's up to the developer to
package the enricher.
We could alleviate this requirement by providing ready-made test enrichers that include
the auxiliary archive packaging. This supplementary dependency could be named using an
additional classifier on the test enricher artifact, as such:
<groupId>org.jboss.arquillian.testenricher</groupId>
<artifactId>arquillian-testenricher-cdi</artifactId>
<classifier>auxiliary-archive</classifier>
<version>...</version>
This will give you not only the test enricher, but also enlistment as an auxiliary
archive. The containers will still do their own packaging...this is for standalone usage.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira