Hi,
You probably have two ways to reference a particular version of a SNAPSHOT
if you need to do so.
1) The "Better Builds with Maven" book
(http://www.mergere.com/m2book_download.jsp), section: 7.6. Team Dependency
Management Using Snapshots"
Reference a specific version such as "xyz-1.0-20060211.131114-1" over
"xyz-1.0-SNAPSHOT"
2) http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins,
section: Deploying the plugin to an internal repository for use within your
company
Use the INTERNAL-r123456 versioning scheme.
I think Option 1 is less disruptive.
Thanks,
Raymond
----- Original Message -----
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, January 08, 2007 9:46 PM
Subject: Re: tuscany-sca revision 493223 does not build? (mvn claims missing
jar dependency)
Jeremy Boynes wrote:
On Jan 8, 2007, at 5:42 PM, Jean-Sebastien Delfino wrote:
Jeremy Boynes wrote:
-1 - this is not the way Maven SNAPSHOTs work.
-- Jeremy
I'm not a maven expert but I think that we need:
- an identification of a particular SNAPSHOT level, xyz-SNAPSHOT
won't work, we need xyz-<level>-SNAPSHOT.
- a way to associate a level with a particular SVN revision,
xyz-r493223-SNAPSHOT is the most obvious to me.
- a way to move levels without scrambling artifact ids, I imagine that
the maven version attribute can be used for that.
Thoughts?
--Jean-Sebastien
What part of what I said are you disagreeing with? the requirements I
was trying to spell out? or the use of revision names in the JAR names?
Raymond was asking to use artifact ids and you didn't -1 that, is this
what you think should be done?
Earlier in this thread (which you just cut out), you said "published
snapshots have a timestamp in the version so it is possible to refer to
an older one if something in the latest causes problems". This will work
as well for me, if there is a good way to associate a timestamped
snapshot with a specific SVN revision (to know what exact level code
we're running with).
Can one of our maven experts help us understand how to get this
timestamp in? is this done with <uniqueVersion>true</uniqueVersion> in
your repository definition?
How do we reference a specific timestamped version?
--Jean-Sebastien
Chill out man - you asked for thoughts and you got mine. Including a SVN
revision number in a SNAPSHOT reference just isn't how Maven works. The
very point of SNAPSHOTs is that they update over time so that people get
the latest version of a project under development. That by definition
makes them unstable and unsuitable for trying to assemble something known
to be working - if you want that, use a release.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I'm perfectly cool. Thanks for your thoughts, I'm just trying to
understand what you're saying and how this modular build scheme is going
to work, and I'm still looking for answers to some of my questions :)
- Are we going to update snapshot Jars over time? or use a
<uniqueVersion>true</uniqueVersion> repository config to publish unique
timestamped versions (which, if I understand correctly will not update
over time)? or do we only want to use releases of pieces of Tuscany to
build working assemblies?
- If we're going to use timestamped snapshots, does anybody know how to
reference a specific timestamp (I couldn't figure this out from the Maven
docs).
- How do people in the group want to associate a specific SVN revision
with a published snapshot? Jeremy, do you know the recommended Maven way
to do that?
Thanks,
--
Jean-Sebastien
---------------------------------------------------------------------
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]
