I think Oleg's suggestion here of putting the spec in the wiki makes
the most sense. I've followed the thread and I think we need to
comment on proposed behavior in one page so we can all see them. I've
already lost track in the mail thread.
On 14-Aug-08, at 2:19 AM, Mark Hobson wrote:
2008/8/13 Michael McCallum <[EMAIL PROTECTED]>:
I wish you would stop pointing that out ;-).
Hehe, forgive me if I'm repeating myself, I'm sure you're more than
aware that this discussion has been going on for quite some time in
many shapes and forms :)
I only use snapshots in local and
never deploy them... if someone wants trunk then they should build it
themselves... if they want to try out the latest development then
take the
next major version of the project which most like is alpha/beta...
Every approach that i have taken is engineered towards allowing
rapid stable,
reproducible change to the deliverables without too much overhead
to the
developers...
I don't use deployed snapshots for the simple reasons that its too
hard to
back track... i want to very easily find out whats changed and
whether
rolling back or forward is the cheapest option... without tags aka
releases
there is just no easy way to do it...
I guess we just use different practices. I use the common scenario of
CI building snapshots for others to digest, since we have so many
components this is a huge benefit. Hopefully Mercury will be able to
satisfy both of our use cases.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
A language that doesn’t affect the way you think about programming is
not worth knowing.
-— Alan Perlis
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
