[ https://issues.jboss.org/browse/SHRINKWRAP-420?page=com.atlassian.jira.pl... ] Marcos Bermudez updated SHRINKWRAP-420: --------------------------------------- Summary: Upgrade to Jboss-parent POM 8 and shrinkwrap-api 1.0.1 and openejb-core 3.1.4 (was: Upgrade to Jboss-parent POM 8 and shrinkwrap-api 1.0.1) Description: Upgrade to Jboss-parent POM 8 and shrinkwrap-api 1.0.1 and openejb-core 3.1.4 In order to use the container-openejb-31 with the version of Arquilian 1.0.2.Final was: Upgrade to Jboss parent 8 and shrinkwrap-api 1.0.1 In order to use the container-openejb-31 with the version of Arquilian 1.0.2.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SHRINKWRAP-420?page=com.atlassian.jira.pl... ] Andrew Rubinger updated SHRINKWRAP-420: --------------------------------------- Summary: Upgrade dependencies of OpenEJB Container (was: Upgrade to Jboss-parent POM 8 and shrinkwrap-api 1.0.1 and openejb-core 3.1.4) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SHRINKWRAP-420?page=com.atlassian.jira.pl... ] Andrew Rubinger commented on SHRINKWRAP-420: -------------------------------------------- Yes, we should upgrade the dependencies and issue a 1.0.0 release. Why is the current state not compatible with Arquillian 1.0.2.Final? OpenEJB is in "provided" scope (it's so the user should be providing/declaring the OpenEJB runtime). Also I'm likely to instead upgrade: * ShrinkWrap to 1.1.0 * JUnit to 4.10 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SHRINKWRAP-420?page=com.atlassian.jira.pl... ] Marcos Bermudez commented on SHRINKWRAP-420: -------------------------------------------- Yes, great! The main problem was the dependency of shrinkwrap-api. Arquillian 1.0.2.Final was compiled with shrinkwrap-api-1.0.1 The last released version of arquilian-container-openejb-1.0.0.Alpha5 uses shrinkwrap-extension-openejb-1.0.0-alpha-12 whitch depends of shrinkwrap-api-1.0.0-alpha-12 In execution of my tests the resolved dependency in classloader is shrinkwrap-api 1.0.1. But when my tests uses shrinkwrap-extension-openejb I get a method not exists exception. I will wait for the release of container-openejb-31-1.0.0 and I will ask arquilian-container-openejb to update the dependencies -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SHRINKWRAP-420?page=com.atlassian.jira.pl... ] Andrew Rubinger commented on SHRINKWRAP-420: -------------------------------------------- Thanks Marcos. To be clear, all's working for you? 1.0.0 of container-openejb-31 has been released. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira