just to note :)
"inContainterITest" != "inContainerITest"
the property name in the command line does not match the property in
the pom.xml, that's why the profile is not activated ;)
Have a nice day!
Žilvinas Vilutis
Mobile: (+370) 652 38353
E-mail: cika...@gmail.com
On Thu, Mar 3, 201
Well, you could also touch a file or mkdir a directory before and use it as
an activation property.
Or even commit something somewhere that would trigger the profile
activation.
Or install a VM that would have the right OS that would activate the
profile.
Or just use the option designed to activat
Hi!
You could give your activation property a value and use
-DinContainerITest=myValue
inContainerITest
myValue
/Thomas
On Thu, Mar 3, 2011 at 17:17, Baptiste MATHUS wrote:
> Hi,
>
> Use -P. Not -D.
>
> Cheers
> Le 2 mars 2011 18:40, "John Lussmyer" a écrit :
> > I've inher
Hi,
Use -P. Not -D.
Cheers
Le 2 mars 2011 18:40, "John Lussmyer" a écrit :
> I've inherited a huge complex Maven build process that needs some updates.
> One thing we have is some custom test code in one place that is invoked
via "mvn clean install -DinContainterITest"
> Now I'd like to invoke t
I've inherited a huge complex Maven build process that needs some updates.
One thing we have is some custom test code in one place that is invoked via
"mvn clean install -DinContainterITest"
Now I'd like to invoke that (and several others in other pom's) from a pom that
is in a different branch o
