Is that an open invitation to help recreate those scripts?
Do others see a need for this? I certainly would like to see us put
them back in geronimo/server/trunk (or genesis) and enhance them to
allow svn checkout/update and orderly building of genesis, specs, server
and even handle openejb
You can create a settings.xml in the default user/.m2 directory to point
to an alternate local repo dir, like -
?xml version=1.0 encoding=UTF-8?
settings
localRepository${LOCAL_GERONIMO_M2_REPO}/localRepository
/settings
But the downside, is you're leaving it up to each developer to
You don't need to add this to settings.xml, you can simply:
mvn -Dmaven.repo.local=some/path
But you are right, to make this work, we need those native scripts to
bootstrap the build again and set the correct value for the repo.
--jason
On Jan 2, 2007, at 8:32 AM, Donald Woods wrote:
Jason V,
Copying you for your feedback and awareness.
On Dec 8, 2006, at 6:06 PM, Jason Dillon wrote:
Maven does not behave well with a mix of default and legacy repos.
I have gone through and moved all legacy repos only to the modules
where they are used, and in some cases imported a
Also, keep in mind that there is no way to bypass the
local repository afaik. So if a bad artifact goes into the
user local repo, it may disturb Geronimo's build, even
if Geronimo build only use a single svn based remote
repo. In such a case, the only way to ensure that the
build will work is
What do you mean? If you specify -Dmaven.repo.local=./svn-repo (or
where ever the svn checkout is) and run the build offline, then the
repo won't get modified, and thus only chance a bad artifact would
get in there would be if someone checked in something bad, or if the
local `mvn
Is there a way to specify that in the pom ?
Or you have to rely on users to specify it on the command
line everytime they build (or use batch files).
On 12/11/06, Jason Dillon [EMAIL PROTECTED] wrote:
What do you mean? If you specify -Dmaven.repo.local=./svn-repo (or
where ever the svn
Unfortunately this would have to be externally controlled, can not
specify maven.repo.local in a pom, and if you could, can't root it to
the project, as ${pom.basedir} will always keep changing.
This was possible in m1 though... for what its worth. Only way to do
this in m2 is to use
On Dec 8, 2006, at 6:41 PM, Prasad Kashyap wrote:
... At this point... and ya, I may be in a
bad mood now... I don't think that mvn is an appropriate tool for
building production quality products... period.
I hear ye. I share the pain. But I fear the alternative - spending
considerable time
Maven does not behave well with a mix of default and legacy repos. I
have gone through and moved all legacy repos only to the modules
where they are used, and in some cases imported a module-local repo
to hold those artifacts so that the build does not need to include a
legacy repo. A
On 12/8/06, Jason Dillon [EMAIL PROTECTED] wrote:
If we are going to continue to use Maven (which I'm starting to
really wonder if it is worth it),
.. (content clipped)...
... At this point... and ya, I may be in a
bad mood now... I don't think that mvn is an appropriate tool for
11 matches
Mail list logo
