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...
On 7/19/07, Johan Iskandar <[EMAIL PROTECTED]> wrote:
I appreciate the reply,
After yet again thinking about it(may be not hard enough :( ), we don't
need to hav
I appreciate the reply,
After yet again thinking about it(may be not hard enough :( ), we don't
need to have version numbers in the sub module poms for reason explained
below.
All we need is for the version number to be at the parent level pom.
And so the sub module poms are tightly coupled to th
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 enfor
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
projects
Continuum users,
For some reason I created a project, deleted it, then created it again.
However somehow now there are two project with the same name and version
numbers in my project list. I'm attaching a screen print, the name of the
project is pvn (version 1.6.1).
Now I cannot dele
Cool! That halfway works. The email is now appearing in continuum.
Unfortunately, it is still including the full list of notifications.
I tried using this:
Continuum
http://saffron.caret.cam.ac.uk/continuum
mail
Hi Aaron,
I'm using the following:
mail
true
true
true
true
[EMAIL PROTECTED]
Regards, Marcel
- Original Message
From: Aaron Zeckoski <[EMAIL PROTECTED]>
To: continuum-users@maven.apache.org
Sen
Hehehe, after thinking about it..
Continuum doesn't need to save state at all(cuz I already assumed at the
beginning that all pom must explicitly state it's current version, so
the parent pom should also have it's version).
BUT, I wonder whether maven encourages an explicit declaration of
version
I dunno how continuum does version releasing but as far as I know about
version releasing is that once you're happy with say build w.x.y.z You
then: (assuming that all pom has its current version explicitly stated
in the file, and it's formatted as p.q.r.s)
-tag all current source &/ pom with an w.
I am trying to find the docs that describe how to setup the continuum
configuration in a maven2 pom correctly. Right now I have the
following in my pom (using maven 2.0.7):
Continuum
http://saffron.caret.cam.ac.uk/continuum
mail
[EMAIL PROTECTED]
However, th
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. you have to do that using hte
maven-release-plugin and you
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
12 matches
Mail list logo
