Jorn, I have implemented the profile in the activemq pom. The profile name running the extended test is: extended-test. If not defined, the default is to run Basic Test as before. I've noticed that Maven launches a separate process to run the tests. So if you kill maven shell with CRL-C, maven does not kill that process just its own shell. See if this true in your case. I suspect you have a java process running with a broker in it. Thats why it says that the port in use..
JC On Fri, Feb 11, 2011 at 11:33 AM, Jörn Kottmann <[email protected]> wrote: > On 2/11/11 4:51 PM, Jaroslaw Cwiklik wrote: > >> Jorn, how would the profile be triggered? If this is per user thing, >> perhaps *.m2/settings.xml is the best place. >> > > You can type -Pextended-test or put something like > this into your settings.xml: > > <settings> > ... > <activeProfiles> > <activeProfile>exented-test</activeProfile> > </activeProfiles> > ... > </settings> > > > Is that ok? > > BTW, the tests are failing on my local machine, and on the build server are > some other issues > with already used ports. > > Jörn >
