> I am trying to use maven 3.0 system dependencies. Here's your solution: don't use system scope. Find another route to the same solution. For me, system scope is another type of profile, and profiles are (can be) evil.
> Only option I found so far (short of defining abc.install in projectA > pom.xml) is to define abc.install as a -D option to the maven command. Then do this. > - Since I need to test a specific product installation, I want to point > directly to all the jar files of that specific product installation so I am > 100% sure that I am actually testing what has been installed. This is why I > want to use the maven system dependency. If you use GAV coordinates with locked-down versions [1.2.3] there should be no question about you "actually testing" something specific. > - I also want to be able to very quickly switch from one product > installation to another (think automated QA suite) which means that I want > to be able to define in a single place (settings.xml through one or more > profiles) the location of that installation I actually think the best scenario would be if you just used the -s parameter to Maven to specify an alternative settings.xml, one per "installation" of your product or libraries, and then used the localRepository configuration for a given localRepo that has been initialized with the specific libraries you are wanting to test: http://maven.apache.org/settings.html#Simple_Values Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
