You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by jieryn <ji...@gmail.com> on 2013/09/13 04:44:55 UTC
TomEE && Surefire && Arquillian
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!
Re: TomEE && Surefire && Arquillian
Posted by jieryn <ji...@gmail.com>.
Hi, I confirm the random port is working. I'm taking other errors with
the -SNAPSHOT, but this aspect works now.
THANKS!
On Tue, Sep 24, 2013 at 2:38 AM, Romain Manni-Bucau
<rm...@gmail.com> wrote:
> Hi
>
> fixed: https://issues.apache.org/jira/browse/TOMEE-1043
>
> thks for the report and the sample! It really helps :)
>
> *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/23 jieryn <ji...@gmail.com>
>
>> I've updated an example project here:
>> https://github.com/jieryn/javaee-example
>>
>> It uses all -SNAPSHOT versions for TomEE, and if you grep the logs for
>> ProtocolHandler you will see that port 8080 is being used. Despite
>> setting the port to -1 via m-surefire-p configuration. TomEE is not
>> obeying system property configuration.
>>
>> On Fri, Sep 13, 2013 at 4:05 AM, Romain Manni-Bucau
>> <rm...@gmail.com> wrote:
>> > 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 <ji...@gmail.com>
>> >
>> >> 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!
>> >>
>>
Re: TomEE && Surefire && Arquillian
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
fixed: https://issues.apache.org/jira/browse/TOMEE-1043
thks for the report and the sample! It really helps :)
*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/23 jieryn <ji...@gmail.com>
> I've updated an example project here:
> https://github.com/jieryn/javaee-example
>
> It uses all -SNAPSHOT versions for TomEE, and if you grep the logs for
> ProtocolHandler you will see that port 8080 is being used. Despite
> setting the port to -1 via m-surefire-p configuration. TomEE is not
> obeying system property configuration.
>
> On Fri, Sep 13, 2013 at 4:05 AM, Romain Manni-Bucau
> <rm...@gmail.com> wrote:
> > 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 <ji...@gmail.com>
> >
> >> 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!
> >>
>
Re: TomEE && Surefire && Arquillian
Posted by jieryn <ji...@gmail.com>.
I've updated an example project here: https://github.com/jieryn/javaee-example
It uses all -SNAPSHOT versions for TomEE, and if you grep the logs for
ProtocolHandler you will see that port 8080 is being used. Despite
setting the port to -1 via m-surefire-p configuration. TomEE is not
obeying system property configuration.
On Fri, Sep 13, 2013 at 4:05 AM, Romain Manni-Bucau
<rm...@gmail.com> wrote:
> 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 <ji...@gmail.com>
>
>> 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!
>>
Re: TomEE && Surefire && Arquillian
Posted by Romain Manni-Bucau <rm...@gmail.com>.
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 <ji...@gmail.com>
> 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!
>