On Thu, Mar 20, 2008 at 3:36 AM, Dan Fabulich [EMAIL PROTECTED] wrote:
Brian E. Fox wrote:
Samuel Le Berrigaud wrote:
1. only run mvn verify, this way nothing gets installed into the local
repository,
This doesn't work in a multi-module reactor build where the modules
depend on
You could do the following...
Copy ~/.m2/settings.xml to ~/.m2/settingsy.xml
Configure localRepository in settingsy.xml to point somewhere else
Copy MAVEN_HOME/bin/mvn.bat to mvny.bat
Edit mvny.bat and append -f ~/.m2/settingsy.xml to the call to mvn
Then call normal mvn from X, and mvny from
You could do even better!
in X create mvn.bat that is just
@echo off
%MAVEN_HOME%\bin\mvn.bat -s %USERPROFILE%\.m2\settings-x.xml %*
create mvn.sh that is just
#!/bin/sh
$MAVEN_HOME/bin/mvn -s ~/.m2/settings-x.xml $*
in Y create mvn.bat that is just
@echo off
folder and install+ will get you a handle to the jar in the local
repo.
-Original Message-
From: Stephen Connolly [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 20, 2008 2:00 AM
To: Maven Users List
Subject: Re: Running two builds of the same branch simultaneously
On Thu, Mar 20, 2008 at 3
I'm working on a multi-module reactor project that has a long build. I'd
like to be able to sync down two copies of trunk (X and Y), do a little
bit of work in X, and start building X. While X builds, I'd like to go
over to Y, do a little bit of work in Y, and kick off a build of Y.
The
Hi Dan,
I see two solutions to this:
1. only run mvn verify, this way nothing gets installed into the local
repository,
2. or run the maven command specifying the local repository on the command
line. Use separate repositories for each build. I don't remember the
property to use on the command
On Wed, Mar 19, 2008 at 8:01 PM, Dan Fabulich [EMAIL PROTECTED] wrote:
The problem with this is the local repository: my X changes may
incorrectly commingle with my Y changes.
Can anyone suggest a way to make this work? If possible, I'd prefer not
to have to login to my box as two
Wendy Smoak wrote:
You can use -Dmaven.repo.local=... to specify a different local
repository on the command line.
Is there some way to wire up a POM to make that be the default for my
project?
-Dan
-
To unsubscribe,
On Wed, Mar 19, 2008 at 8:22 PM, Dan Fabulich [EMAIL PROTECTED] wrote:
Wendy Smoak wrote:
You can use -Dmaven.repo.local=... to specify a different local
repository on the command line.
Is there some way to wire up a POM to make that be the default for my
project?
Not really. It's
Wendy Smoak wrote:
Not really. It's developer-specific, so it goes in settings.xml (or on
the command line).
Too bad...
It wouldn't make sense in the pom, which needs to work for all
developers.
Sure it would; you'd set the local repo to be ./localrepo.
-Dan
Samuel Le Berrigaud wrote:
1. only run mvn verify, this way nothing gets installed into the local
repository,
This doesn't work in a multi-module reactor build where the modules depend
on each other, does it?
I've got a project X that depends on project Y; project Y built (without
No, it will only work if you at least do compile (then a reference to
/target/classes is passed instead of the jar)
-Original Message-
From: Dan Fabulich [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2008 11:32 PM
To: Maven Users List
Subject: Re: Running two builds of the same
Brian E. Fox wrote:
Samuel Le Berrigaud wrote:
1. only run mvn verify, this way nothing gets installed into the local
repository,
This doesn't work in a multi-module reactor build where the modules
depend on each other, does it?
No, it will only work if you at least do compile (then a
13 matches
Mail list logo
