But if a new test case is introduced then the maintainer of the
1.2.3.4
pom should increment the bug-fix number (or whatever name is best used
here) so the new version would be 1.2.4.0
I mean the maintainer should trigger maven to increment the bug-fix
number
He himself doesn't need to
-Original Message-
From: Jesse McConnell [mailto:[EMAIL PROTECTED]
ah, I basically see what your problem is...
that is what the whole SNAPSHOT concept addresses...
where you are saying a project would only care about 1.2.3 and not the
build numbers..that is functionally
there have been threads on this on the maven-users and maven-dev lists...
in fact Kenny has written extensively on this topic I believe :)
if your interested in contributing to this effort, I would take a look
there for places to help out.
the fundamental problem your dealing with is that
-Original Message-
From: Jesse McConnell [mailto:[EMAIL PROTECTED]
there have been threads on this on the maven-users and maven-dev
lists...
in fact Kenny has written extensively on this topic I believe :)
I've searched the web for Kenny, version, maven-dev, maven-user and my
On 18/07/07, Jesse McConnell [EMAIL PROTECTED] wrote:
at the moment I think you need to make sure the underlying project
that you are going to try and release is 'clean' for the release.
that means that all dependencies that you are going to release ave
been resolved into released and available
: Maven2 release process in Continuum
On 18/07/07, Jesse McConnell [EMAIL PROTECTED] wrote:
at the moment I think you need to make sure the underlying project
that you are going to try and release is 'clean' for the release.
that means that all dependencies that you are going to release ave
been
:54 PM
To: continuum-users@maven.apache.org
Subject: Re: Maven2 release process in Continuum
On 18/07/07, Jesse McConnell [EMAIL PROTECTED] wrote:
at the moment I think you need to make sure the underlying project
that you are going to try and release is 'clean' for the release
are you making good use of dependencyManagement? This should let you
centralize the majority of actual version information and make it easy
to release.
as for speed of releasing I have released quite large multi module
builds in a phased approach where I had to resolve snapshots between
Hello,
Johan Iskandar [EMAIL PROTECTED] writes:
BUT, I wonder whether maven encourages an explicit declaration of
version in the pom(just as the above assumption)? Please advise? Also
why does it use SNAPSHOT instead of build version..(the letter z in my
example)?
Yes, maven enforces an
at the moment I think you need to make sure the underlying project
that you are going to try and release is 'clean' for the release.
that means that all dependencies that you are going to release ave
been resolved into released and available artifacts.
the continuum release mechanism makes use
10 matches
Mail list logo
