[ https://issues.jboss.org/browse/ARQ-889?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-889: ------------------------------ Priority: Critical (was: Major) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ARQ-889?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen edited comment on ARQ-889 at 4/25/12 1:25 PM: ------------------------------------------------------------ I've upped it to critical, not that that really means anything. We're well aware of the issue, but still Arquillian require ShrinkWrap Descriptors and ShrinkWrap to release a new v before we can do anything. was (Author: aslak): I've upped it to blocker, not that that really means anything. We're well aware of the issue, but still Arquillian require ShrinkWrap Descriptors and ShrinkWrap to release a new v before we can do anything. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ARQ-889?page=com.atlassian.jira.plugin.sy... ] Samuel Santos commented on ARQ-889: ----------------------------------- @Gunnar, the quick fix above will work exactly as expected. Define Arquillian BOM normally: {code} <dependencyManagement> <dependencies> <dependency> <groupId>org.jboss.arquillian</groupId> <artifactId>arquillian-bom</artifactId> <version>1.0.0.Final</version> <scope>import</scope> <type>pom</type> </dependency> </dependencies> </dependencyManagement> {code} Add your Arquillian dependency with the scope test: {code} <dependencies> <dependency> <groupId>org.jboss.arquillian.testng</groupId> <artifactId>arquillian-testng-container</artifactId> <scope>test</scope> </dependency> </dependencies> {code} And you will end up with all the needed JARs in your classpath with test scope. Removing the scope import from ShrinkWrap BOMs, will not cause the dependencies to be removed from your classpath. It's only a way to allow you to override their scopes with <scope>test</scope>, which is defined in arquillian-testng-container dependency. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ARQ-889?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-889: ------------------------------ Fix Version/s: 1.0.1.Final (was: 1.1.0.Beta1) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ARQ-889?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen edited comment on ARQ-889 at 6/1/12 2:44 AM: ----------------------------------------------------------- pushed upstream https://github.com/arquillian/arquillian-core/commit/e0032d97bb10b08c6bfb... was (Author: aslak): pushed upstream -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira