Document jars needed between 'test-framework-bom' and 'container-profile-bom' for build system with no DependencyManagement --------------------------------------------------------------------------------------------------------------------------- Key: ARQ-463 URL: https://issues.jboss.org/browse/ARQ-463 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 1.0.0.CR1 Reporter: Aslak Knutsen The only thing missing is that we still don't have a well-documented way of listing which dependencies are required if you didn't want to use a dependency management system. My vision for this is a script which will pull down the dependencies you need for a given container and stick them in a folder somewhere. Obviously, you limit your ability to use different containers, which I don't think needs to be our concern. In fact, the best way to resolve it is to simply be able to produce a report of which JARs are used, with links to download them. Combine the 'container-profile-bom' with the 'test-framework-bom' and grind it through some dep resolver ('dependency:tree') and we should have a somewhat report of what is needed. http://www.jboss.org/tattletale ? * You probably don't want to add those 250 container libs, but rather depend on jboss-client.jar found in $JBOSS_HOME/client -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira