Product: Maven 1.0-rc1
MAVEN_HOME = /java/maven MAVEN_HOME_LOCAL = <not set>
During a build, it seems that Maven will ignore MAVEN_HOME when it copies the result to the repository cache. Instead it copies to ${user.home}/.maven
Internally in Avalon Merlin, we have a resolution of;
maven.home.local -> maven.home -> ${user.home}/.maven
which is not behaving in the same manner as Maven's build system.
This is posing a very subtle annoyance for Merlin users who has MAVEN_HOME variable set, but not the MAVEN_HOME_LOCAL.
So.... True / false for the following statements would be appreciated.
1. You are not allowed to set MAVEN_HOME only. You either set both MAVEN_HOME and MAVEN_HOME_LOCAL, or none.
2. Maven's build system has this bug and it has been corrected.
3. Maven's build system has this bug and it will be corrected.
4. "Maven Folks" doesn't understand the problem we are facing.
5. we have misunderstood the resolution if MAVEN_HOME_LOCAL is not set, and should fallback straight to ${user.home}/.maven without considering MAVEN_HOME.
Cheers Avalon Development Team
(message forward from Niclas Hedhman)
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/ | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
