Not starting with a letter, but letters are used in the version of the Xpp3
parser:
http://www.extreme.indiana.edu/dist/java-repository/xpp3/jars/
Yes I'm extremely familiar with Xpp3... I've even filed a few bugs
against it a while back when the versions and classifiers in the poms
weren't
Hi,
Personally, I would be pragmatic about this and just adopt the
Maven-style versioning so that release would work properly. Or you
could hack the release plugin code, add this functionality, and
contribute it back via JIRA as an enhancement.
It's not so easy, when you change version
Not looking to start an ideological war or anything, but can someone
perhaps point out a major project (or two) that uses versions which
start with a letter? Major being something with a few thousand
customers or something, and open source would be ideal but closed
source works so long as the
Wayne,
There are several cases where the --batch-mode auto stuff of maven doesn't
work in quite a desirable way so the aforementioned flag would be
GREATLY appreciated.
Examples:
1) 1.0-SNAPSHOT would be auto set to 1.1-SNAPSHOT, but many times we'd like
it to go to 1.0.1-SNAPSHOT
2)
Indeed,
Indeed there are few projects that use a letter to start the version number,
but it's not my choice and I can't change that (immediatly). But it's true
that like Daniel said, even with a maven-style versionning convention there
are some cases where it could be a good thing to be able
Hi Wayne,
Wayne Fay wrote on Monday, March 05, 2007 4:35 PM:
Not looking to start an ideological war or anything, but can someone
perhaps point out a major project (or two) that uses versions which
start with a letter? Major being something with a few thousand
customers or something, and
Hi all,
Here my problem, I would like to specify the next version of my project when I
release with the maven 2 release plugin in batch mode (in a continuous
integration process) because it does not handle my incrementation convention.
In fact It can not parse the version number for
If it doesn't, it should.
On 3/2/07, Elid OR [EMAIL PROTECTED] wrote:
Hi all,
Here my problem, I would like to specify the next version of my project
when I
release with the maven 2 release plugin in batch mode (in a continuous
integration process) because it does not handle my incrementation
I don't know if I entirely agree with that.
Maven is not just a tool to help you compile and build your Java
projects -- it also gently enforces a collection of best practices
for building Java projects. It seems like your version starting with
a letter does not meet Maven's concept of best
I suppose that depends on who's best practices they are, which best
practices they are, and how important they are. I'd really hate to put an
issue like the format of a release number on the same par as doing a release
without running the tests.
Quite frankly, the version starting with a letter
10 matches
Mail list logo
