Hello, I am actually trying to implement this solution and I am having a small problem I was wondering if you could help me. I taken a small project and set the maven.jar.override=on, maven.jar.toolkit=SNAPSHOT inside the project.properties file. However, when I run any maven command a strange SNAPSHOT file shows up in my current directory. I renamed this SNAPSHOT file and sure enough it is a jar file. I am just not sure I am using the override setting properly. Should what I am doing work? Would you mind sending me a small snippet of a project.properties file that this works in? Thanks Brian
-----Original Message----- From: STRAYER, JON (SBCSI) [mailto:[EMAIL PROTECTED] Sent: Thursday, December 09, 2004 11:49 AM To: Maven Users List Subject: SNAPSHOTS to versions back to SNAPSHOTS FYI We use CruiseControl to automate our continuous integration builds. For these builds we want to use SNAPSHOT dependencies for our internal libraries. But when we release an application we resolve all the SNAPSHOTS to specific released versions. This leads to us having to change everything back to SNAPSHOT after the release. This is something of a pain in the rear. I was looking for a plugin to automate at least some of this work, but as of 1.0.2 I have a better idea. I'm using jar overrides in my main project.properties file to set the override for each of our libraries to SNAPSHOT, but it also sets maven.jar.override=off. The script that starts CruiseControl sets MAVEN_OPTS to -Dmaven.jar.override=on So, when Cruisecontrol does a build it uses SNAPSHOTS. But a normal run of Maven uses the values from project.xml. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
