I've run into a strange problem with a fresh installation of m2. Some of our unit tests require machine-specific system properties which we usually supply at the command-line, e.g. mvn install -Dmy.prop=value I recently emptied the local repository on one of the (AMD64) machines (running FC4), installed Maven 2.0.4 and allowed it to download all the necessary dependencies. On that machine, properties defined at the command line are not passed along to the unit tests, whereas I had no such problem before I cleared out the repository. It makes no difference whether I use Maven 2.0.2, 2.0.3 or 2.0.4. A fresh installation of Maven 2.0.2 on an x86 Ubuntu machine has the same problem. A third machine (FC4 on x86) has used Maven 2.0.2 since I installed it months ago, and picks up the properties as it should. I've reproduced the error with a minimal project on the machines with newer repositories, and again there is no problem on the machine with the newer repository. All three machines are using the junit plugin v. 3.8.1. Copying over the entire repository from the working machine to a broken machine fixes the problem. Any ideas which plugin is to blame? Thanks,
Josh --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
