Re: Feature request: per-module local version in profile

2007-01-31 Thread Mark Lundquist
Ralph Goers wrote: export MAVEN_OPTS=-Dmaven.repo.local=$PWD/.mvn Mark Lundquist wrote: So my argument is that my expectation that builds would be self-contained was reasonable. And in fact, separate builds on separate machines *are* (by default) self-contained! I am arguing that it

Re: Feature request: per-module local version in profile

2007-01-30 Thread Mark Lundquist
Hi Ralph, Ralph Goers wrote: Mark Lundquist wrote: IIUC, SNAPSHOT is concerned w/ the relationship btwn. remote and local repositories. That's not in view here. Huh? SNAPSHOT identifies an artifact as not-released. There is no requirement that it ever be published to a r

Re: Feature request: per-module local version in profile

2007-01-29 Thread Mark Lundquist
Andrew Williams wrote: have you tried referring to a snapshot build using it's full build identifier (date etc)? that has worked for me in some situations in the past. "Referring to"? No touching the pom, that's my requirement :-) I'm looking for a solution, not a kludge that might help in

Re: Feature request: per-module local version in profile

2007-01-29 Thread Mark Lundquist
Ralph Goers wrote: Mark Lundquist wrote: It's not. Did you read the scenario from my original post? I don't think SNAPSHOT is even in view here. Yes, I read it. IIUC, SNAPSHOT is concerned w/ the relationship btwn. remote and local repositories. That's not in view h

Re: Feature request: per-module local version in profile

2007-01-29 Thread Mark Lundquist
Mark Lundquist wrote: -JIRA-1234 foo bar biff OK, having already dispensed w/ the "prefix" idea in favor of an across-the-board build-specific private version ID, we can simplify this some more.

Re: Feature request: per-module local version in profile

2007-01-29 Thread Mark Lundquist
late last night I, Mark Lundquist wrote: thinking about it some more, maybe the version to use should be specified as a suffix to be applied to whatever the model-determined artifact ID would otherwise be. That's the only reasonable way to be able to apply this to an aggregate of mo

Re: Feature request: per-module local version in profile

2007-01-29 Thread Mark Lundquist
Hi Ralph, fancy meeting you here :-)... Ralph Goers wrote: I have one issue with this. Typically, at least in the environment I work in (which uses Maven 1), the version would be something like 1.0.1 only when that version had been released. When doing any modifications the version should bec

Re: Feature request: per-module local version in profile

2007-01-29 Thread Mark Lundquist
Patrick Schneider wrote: On 1/28/07, Mark Lundquist <[EMAIL PROTECTED]> wrote: [..snip] To pull this off, I need to be able to say "in this working area, module M builds version V (some local custom version name), *and* all other modules that depend on P must resolve that de

Feature request: per-module local version in profile

2007-01-28 Thread Mark Lundquist
Hi, I think I've identified a need for a new (hopefully minor) Maven feature that I'd like to discuss. I've failed to find any solution with the current feature set (but please let me know if I'm wrong about that! :-), and although I'm new to the internals of Maven I'd be happy to contribute

Now what? (Re: Trouble building Maven 2 trunk)

2006-08-28 Thread Mark Lundquist
So, what next? How do I invoke the Maven I have just built? I tried ./maven-cli/src/bin/mvn ...and got Exception in thread "main" java.lang.NoClassDefFoundError: org/codehaus/classworlds/Launcher So I guess that wasn't the right thing to do :-) help? —ml—

Re: Trouble building Maven 2 trunk

2006-08-28 Thread Mark Lundquist
Dennis Lundberg wrote: Mark, I see that you are using Planet Mirror as you central repo. They recently made some changes which makes it impossible to download certain files. Please use another mirror, until their problems have been fixed. OK... I commented out the Planet Mirror section in

Re: Trouble building Maven 2 trunk

2006-08-28 Thread Mark Lundquist
Brett Porter wrote: Sorry, I'm not quite sure what's happened to you here. The POM should have a parent of version 4, and that should in turn have a parent org:apache:apache, version 3. When I remove them from my local repo it successfully downloads them again. You might want to run wit

Re: Trouble building Maven 2 trunk

2006-08-27 Thread Mark Lundquist
Brett Porter wrote: The parent POM has been released, so we need to update that to 4 instead of 4-SNAPSHOT... - Brett Hey thanks Brett & Vincent... OK, looks like that happened, I picked it up w/ "svn up". Still no go. So then I changed it back to 4-SNAPSHOT and tried again with -Papach

Trouble building Maven 2 trunk

2006-08-26 Thread Mark Lundquist
Hi, I did a clean checkout of components/, did "mvn -X install", and got the error trace shown below. I've renamed my settings.xml out of the way, so it should be defaults for everything... any ideas? Am I doing something wrong? thx, Mark -- + Error stacktraces are turned on. Maven v

Bad link on "About Maven 2.0" page

2006-08-26 Thread Mark Lundquist
Hi, I am totally new to the ways of Maven! Anyway... On http://maven.apache.org/about.html, under "Can I get involved", the text "For more information, please see How to Help." contains a link to a bad URI (http://maven.apache.org/contributing/help.html). The link should be to http://maven.a