Hi,
While I was running this command D:/proyek/mvn verify, I was hoping to
find my surefire tests runs having in one of it's classpaths the path
D:/proyek/proyek-core/target/classes.
I tested this by invoking the code in one of it's test classes:
==
URL url =
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
-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
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
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)?
Thanks
-Original Message-
From: Johan Iskandar
Sent: Wednesday, July 18, 2007 4:04 PM
To: continuum-users@maven.apache.org
Subject: RE
Hi,
I was following the links from here for tutorials on continuum:
http://docs.codehaus.org/display/CONTINUUM/Home
then in Where is the documentation on how to use the latest Continuum?
It pointed me to:
http://docs.codehaus.org/display/CONTINUUMUSER/Building
but when I checked out the
