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.

Andy

Mark Lundquist wrote:
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 become 1.0.2-SNAPSHOT until the next release is performed.

No -- you're talking about versions in the poms, which are controlled resources. I am talking about modifications that are *strictly local* to a user's personal build. Indeed the mechanism that I'm proposing would apply to artifacts that already have a SNAPSHOT version from the repository, e.g. the local artifact version for my "foobar" build would become "1.0.2-SNAPSHOT-foobar" or whatever.

You aren't supposed to tack on things like a Jira number.

No, not in a published artifact... but that's not what I'm talking about. I'm trying to uniquify the artifacts within my own local repo so that I can have multiple builds sharing a local repo and not interfering with each other.

SNAPSHOT should be sufficient to tell maven how to behave.

It's not. Did you read the scenario from my original post? I don't think SNAPSHOT is even in view here.

Do you think it's currently possible to build two different instances of a project (e.g. one w/ local modifications and one without) on the same machine without them stomping on each other in the repository, (a) without touching any other controlled resource (such as a pom :-) not directly related to the modification in question (i.e., that I would not include in a patch file), and (b) in a location-based way (i.e. that doesn't require me to remember to say some kind of "maven -Dblah.blah"? If so, please tell me how! :-)

cheers,
—ml—



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to