On Fri, Nov 18, 2005 at 12:20:39AM -0800, Bill Barker wrote:
> "Stefan Bodewig" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > On Wed, 16 Nov 2005, Leo Simons <[EMAIL PROTECTED]> wrote:
> >
> >> --> support for maven2 in gump2
> >> --> I'm not going to work on it
> >
> > I'd offer to do a monkey-see-monkey-do support if it is not too
> > different from maven 1 support. In general I agree that gump3 is the
> > way to go and that we should do it properly.
> >
> > It depends on how quickly we are going to need it. As soon as
> > projects in our tree switch to Maven2 exclusively, we will at least
> > need that quick-hack version.
>
> I believe that both the Maven1 and Maven2 scripts use $MAVEN_HOME, which is
> the biggest problem with just creating a <mvn/> tag for Gump2. There are
> also problems with separating the local Maven repository between Gump1 and
> Gump2. As much as I hate to admit it, having a <mvn/> tag in Gump2 looks
> like it will be a lot of work :(.
Do I understand correctly that the problem you see is that
-> you need different values of MAVEN_HOME
-> you need different contents of ~/.maven
if so, that isn't something you can't hack in there I think. Just create
~/.maven1
~/.maven2
prior to invoking maven1:
rm -f ~/.maven
ln -s ~/.maven1 ~/.maven
export MAVEN_HOME=foo
prior to invoking maven2:
rm -f ~/.maven
ln -s ~/.maven2 ~/.maven
export MAVEN_HOME=bar
the equivalents in python involve something like
os.unlink(fnmatch('~/.maven'))
os.symlink('~/.maven', '~/maven2')
os.environ["MAVE_HOME"] = 'foo'
relevant docs at
http://docs.python.org/lib/module-os.html
LSD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
