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
---------------------------------------------------------------------
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]
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
