+1 here. Jez was indicating that it was "Crucial" that a snapshot build not get 
"rebuilt" when creating the release and simply get promoted to a release. That 
is simply not that way maven currently works. I hope that is now clear.

I do like the idea though of rebuilting a CD build after a successful CI build. 
I think that has potential.

> -----Original Message-----
> From: stug23 [mailto:[email protected]]
> Sent: Monday, November 08, 2010 2:21 PM
> To: [email protected]
> Subject: Re: Continuous Delivery and Maven
> 
> 
> We need to figure out how to best leverage Maven (keeping in mind its
> process
> and practices) in a Continuous Delivery solution. I like the conversation
> around this topic and also see that there is this other discussion about
> the
> meaning of CD versus CI.
> 
> From the comments so far, there has been a fair amount of discussion
> about
> how to use SNAPSHOTs as if they were something that they aren't. Namely
> retaining SNAPSHOTs all the way through release, possibly mutating the
> metadata to make the builds products look like released artifacts instead
> of
> SNAPSHOTs without having to rebuild the binaries. Since a SNAPSHOT works
> well for a "work in progress" and not for a "thing I want to keep", maybe
> a
> different approach would work better.
> 
> Maybe it would make more sense to just burn lots of version numbers (e.g,
> 3.5.1099) and always release with a new yet-to-be-defined Maven release
> plugin that reflects the processes involved with CD. If the concern is
> disk
> usage or inefficiency, perhaps some automation can make this more
> manageable?
> 
> I would be interested in inputs on this topic from the Maven founders if
> they are following this thread.
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Continuous-Delivery-and-Maven-
> tp3245370p3255592.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
> 
> ---------------------------------------------------------------------
> 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