Hi 1.6.0.beta1 is not official and will probably not be released, do you encounter this issue on trunk?
*Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/9/13 jieryn <[email protected]> > Greetings, > > TomEE 1.6.0.beta1 and all the latest Arquillian and Surefire plugins > are in use. I'm following the instructions here: > > https://tomee.apache.org/arquillian-available-adapters.html > > Despite the claims, TomEE does not obey m-surefire-p configuration for > tomee: > > <plugin> > <artifactId>maven-surefire-plugin</artifactId> > <version>2.16</version> > <configuration> > <systemPropertyVariables> > <tomee.embedded.httpPort>-1</tomee.embedded.httpPort> > <tomee.embedded.stopPort>-1</tomee.embedded.stopPort> > <tomee.httpPort>-1</tomee.httpPort> > <tomee.stopPort>-1</tomee.stopPort> > </systemPropertyVariables> > </configuration> > </plugin> > > Nor does it obey if I specify command line arguments: > > mvn -Dtomee.httpPort=14000 -Dtomee.stopPort=14001 > -Dtomee.embedded.httpPort=10000 -Dtomee.embedded.stopPort=10001 clean > install > > It only obeys when I code up a src/test/resources/arquillian.xml: > > <?xml version="1.0"?> > <arquillian xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns="http://jboss.org/schema/arquillian"; > xsi:schemaLocation="http://jboss.org/schema/arquillian > http://jboss.org/schema/arquillian/arquillian_1_0.xsd";> > <container qualifier="tomee" default="true"> > <configuration> > <property name="httpPort">-1</property> > <property name="stopPort">-1</property> > </configuration> > </container> > </arquillian> > > Can someone confirm this is a bug? Thanks! >
