-
Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
None
It is currently very unpractical to use Arquillian for any project that does not use mvn for it's own build. There is a lot of information around the net "how to use with ant only" (which proves the demand) but in the end this is a list of some 10-20 individual artifacts that one is to locate individually from Nexus.
Naturally, the information varies with Arquillian version, and no info is to be found for the "latest stable" and so sends everybody on her/his own hunt.
Providing an arquillian-uberjar-$version.jar would really help here.
This should not be too much trouble for someone fluent with mvn, but those who do not want to use maven are also those who can't figure it out for themselves...
Of course, having an arquillian-base and separate arquillian-jboss7 / arquillian-tomcat ... jar would be preferable to having one uberjar ... whatever ... but even the uberjar would be a good start ... for starters ...
Providing a shell script that builds those from latest stable (with mvn under the hood) would also be acceptable of course (kind of like jboss-as has).
Maybe that is even easy from Arquillian sources, but again, some kind of information for the new user is required...
- relates to
-
ARQ-463 Document jars needed between 'test-framework-bom' and 'container-profile-bom' for build system with no DependencyManagement
- Open