I found a "work around" on my own. Actually in retrospect I realize that
this is the Maven way to do this. The solution is to set up profiles in
your POM that create the required system variables. Then just invoke the
profile with the -Pprofile_id argument to Maven.
We have experience the same thing. We are using arguments to categorize our
unit tests. This has stopped working when we upgraded to 2.2.0.
Anyone have a workaround?
Hmmm, we noticed that passing any args like
mvn -Dblah=didah
works fine up to 2.0.9, but is broken thereafter. Anyone ran into the same
issue?
--
=NPG=
--
View this message in context:
http://www.nabble.com/Maven2-ignoring-environment-variables-tp22845174p24591876.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
