On 19/07/07, Jesse McConnell <[EMAIL PROTECTED]> wrote:
are you making good use of dependencyManagement? This should let you
centralize the majority of actual version information and make it easy
to release.
I hope so, but I have 2 months Maven experience, so there are
doubtless areas for imp
On 18/07/07, Mykel Alvis <[EMAIL PROTECTED]> wrote:
> 1) There is potential for me to check in the release version, start
> preparing the release and then someone else checks out the release
> version and starts doing stuff to it, when they should really be
> waiting until the next SNAPSHOT versi
t version it is
in..1.2.3.5 or 1.2.4.0
Is my point clearer?
johan
> -Original Message-
> From: Jesse McConnell [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 19, 2007 2:17 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Maven2 release process in Continuum
>
> what as
what aspect of maven do you think is killing this use case?
1.2.3.4-SNAPSHOT when its run through the release process will offer
up as a default 1.2.3.5-SNAPSHOT as the new development version and
1.2.3.4 as the released version...
deployment will work...whats killing this for you?
and the rele
> From: Jesse McConnell [mailto:[EMAIL PROTECTED]
>
> ok, I am a bit confused by what your actually asking here...
>
> but there is no reason in the world you can't use w.x.y.z
versioning...
>
Well, since maven's main idea is to promote conventions.. and these
conventions is there to ease and
1) There is potential for me to check in the release version, start
preparing the release and then someone else checks out the release
version and starts doing stuff to it, when they should really be
waiting until the next SNAPSHOT version has been checked in. I guess I
can use locking for that, b
On 18/07/07, Jesse McConnell <[EMAIL PROTECTED]> wrote:
if you have one company pom...
and 17 projects to releaseand those 17 projects each use a
snapshot version of the company pom..
you currently need to checkout all 17 poms, edit the parent pom to a
released version and check them in. y
