Please commit to the Maven Version Numbers Scheme :-)
The Saxon XSLT and XQuery processor, developed by Saxonica
Brought to you by:
mhkay
Menu
▾
▴
#23 Please commit to the Maven Version Numbers Scheme :-)
Maven is rather common today, and one of its best features is the ability to automatically download and use the latest bug fix of a dependency. Hence, one can rely to only get the latest bug fixes, but no (possible incompatible) API changes, when following some simple common rules.
The most important rule is void by SAXON. It is that the version schema must be:
MAJOR.MINOR.BUGFIX-BUILD
This is essential to allow Maven to detect "later" versions (hence, deal with the parts and four single integers but not as one large string).
Unfortunately SAXON is using the following schema:
MAJOR.MINOR.BUGFIX.BUILD
...hence Maven cannot detect that 9.4.0.2 is actually the second build of 9.4.0, and fails to automatically download any bug fixes of 9.4 when instructed to do so using the range [9.4, 9.5). :-(
It would be really great if you could commit to the "right" schema when uploading versions into Maven Central. That means, you can leave all as it is, but just have to provide the dashed version number (instead of the dotted) in the POM. :-)
Hi Markus,
Thanks for the point you have raised regarding maven setup.
It is our endeavour to get it right when it comes to Saxon on maven. Therefore for the next maintenance release of Saxon we will look into your comments and resolve this issue.
Just to clarify your suggestion would the following be acceptable for Saxon:
MAJOR.MINOR.BUGFIX,BUILD
For example,
9.5.0,3
With issues relating to Saxon products we prefer that they be raised on our Saxon community site:
https://saxonica.plan.io/
Specifically the Saxon forum is a great place to discuss such topic:
https://saxonica.plan.io/projects/saxon/boards
Hi,
thank you for picking this up.
Unfortunately Maven will only work correctly if the separation between
BUGFIX and BUILD is a DASH not a COMMA!
Hence, it must exactly be MAJOR.MINOR.BUGFIX-BUILD.
HTH
-Markus
From: oneil [mailto:ond1@users.sf.net]
Sent: Montag, 3. Juni 2013 15:46
To: [saxon:feature-requests]
Subject: [saxon:feature-requests] Re: #23 Please commit to the Maven Version
Numbers Scheme :-)
Hi Markus,
Thanks for the point you have raised regarding maven setup.
It is our endeavour to get it right when it comes to Saxon on maven.
Therefore for the next maintenance release of Saxon we will look into
your comments and resolve this issue.
Just to clarify would the following be acceptable for Saxon:
MAJOR.MINOR.BUGFIX,BUILD
For example,
9.5.0,3
With issues relating to Saxon products we prefer that they be raised on
our Saxon community site:
https://saxonica.plan.io/
Specifically the Saxon forum is a great place to discuss such topic:
https://saxonica.plan.io/projects/saxon/boards
On 31/05/13 14:41, Markus KARG wrote:
[feature-requests:#23] http://sourceforge.net/p/saxon/feature-requests/23/
http://sourceforge.net/p/saxon/feature-requests/23/ Please commit to
the Maven Version Numbers Scheme :-)
Status: open
Created: Fri May 31, 2013 01:41 PM UTC by Markus KARG
Last Updated: Fri May 31, 2013 01:41 PM UTC
Owner: nobody
Maven is rather common today, and one of its best features is the
ability to automatically download and use the latest bug fix of a
dependency. Hence, one can rely to only get the latest bug fixes, but
no (possible incompatible) API changes, when following some simple
common rules.
The most important rule is void by SAXON. It is that the version
schema must be:
MAJOR.MINOR.BUGFIX-BUILD
This is essential to allow Maven to detect "later" versions (hence,
deal with the parts and four single integers but not as one large string).
Unfortunately SAXON is using the following schema:
MAJOR.MINOR.BUGFIX.BUILD
...hence Maven cannot detect that 9.4.0.2 is actually the second build
of 9.4.0, and fails to automatically download any bug fixes of 9.4
when instructed to do so using the range [9.4, 9.5). :-(
It would be really great if you could commit to the "right" schema
when uploading versions into Maven Central. That means, you can leave
all as it is, but just have to provide the dashed version number
(instead of the dotted) in the POM. :-)
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/saxon/feature-requests/23/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
--
O'Neil Delpratt
Software Developer, Saxonica Limited
Email: oneil@saxonica.com oneil@saxonica.com
Tel: +44 118 946 5894
Web: http://www.saxonica.com
Saxonica Community Site: http://dev.saxonica.com Saxonica Bug tracking
System: https://saxonica.plan.io/
[feature-requests:#23] http://sourceforge.net/p/saxon/feature-requests/23/
Please commit to the Maven Version Numbers Scheme :-)
Status: open
Created: Fri May 31, 2013 01:41 PM UTC by Markus KARG
Last Updated: Mon Jun 03, 2013 01:34 PM UTC
Owner: nobody
Maven is rather common today, and one of its best features is the ability to
automatically download and use the latest bug fix of a dependency. Hence,
one can rely to only get the latest bug fixes, but no (possible
incompatible) API changes, when following some simple common rules.
The most important rule is void by SAXON. It is that the version schema must
be:
MAJOR.MINOR.BUGFIX-BUILD
This is essential to allow Maven to detect "later" versions (hence, deal
with the parts and four single integers but not as one large string).
Unfortunately SAXON is using the following schema:
MAJOR.MINOR.BUGFIX.BUILD
...hence Maven cannot detect that 9.4.0.2 is actually the second build of
9.4.0, and fails to automatically download any bug fixes of 9.4 when
instructed to do so using the range [9.4, 9.5). :-(
It would be really great if you could commit to the "right" schema when
uploading versions into Maven Central. That means, you can leave all as it
is, but just have to provide the dashed version number (instead of the
dotted) in the POM. :-)
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/saxon/feature-requests/23/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
Related
Feature Requests: #23
We'll consider this, but I'm initially reluctant. The majority of our users do not use Maven and I'm reluctant to inflict a change in established processes to make Saxon fit better with Maven. Saxon also has to fit with other environments with other conventions, for example .NET.
Ok seems I was not clear enough. There is NO NEED to change anything
outside of the Maven world -- leave it all as it is! The trick simply is to
ONLY correct the POM file (i. e. the file that describes SAXON's meta
information like name and version within the Maven universe) but not to
touch anything else. Hence, the JAR's name, and the versions everywhere
besides Maven, will always stick to the schema you apply currently. The
change proposed is ONLY visible to the Maven tool chain. So, people outside
Maven are not touched by this! If you need, I can show you the needed
changes in the POM file. :-)
HTH
-Markus
From: Michael Kay [mailto:mhkay@users.sf.net]
Sent: Montag, 3. Juni 2013 19:24
To: [saxon:feature-requests]
Subject: [saxon:feature-requests] #23 Please commit to the Maven Version
Numbers Scheme :-)
We'll consider this, but I'm initially reluctant. The majority of our users
do not use Maven and I'm reluctant to inflict a change in established
processes to make Saxon fit better with Maven. Saxon also has to fit with
other environments with other conventions, for example .NET.
[feature-requests:#23] http://sourceforge.net/p/saxon/feature-requests/23/
Please commit to the Maven Version Numbers Scheme :-)
Status: open
Created: Fri May 31, 2013 01:41 PM UTC by Markus KARG
Last Updated: Mon Jun 03, 2013 01:34 PM UTC
Owner: nobody
Maven is rather common today, and one of its best features is the ability to
automatically download and use the latest bug fix of a dependency. Hence,
one can rely to only get the latest bug fixes, but no (possible
incompatible) API changes, when following some simple common rules.
The most important rule is void by SAXON. It is that the version schema must
be:
MAJOR.MINOR.BUGFIX-BUILD
This is essential to allow Maven to detect "later" versions (hence, deal
with the parts and four single integers but not as one large string).
Unfortunately SAXON is using the following schema:
MAJOR.MINOR.BUGFIX.BUILD
...hence Maven cannot detect that 9.4.0.2 is actually the second build of
9.4.0, and fails to automatically download any bug fixes of 9.4 when
instructed to do so using the range [9.4, 9.5). :-(
It would be really great if you could commit to the "right" schema when
uploading versions into Maven Central. That means, you can leave all as it
is, but just have to provide the dashed version number (instead of the
dotted) in the POM. :-)
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/saxon/feature-requests/23/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
Related
Feature Requests: #23
Hi Markus,
Just to let you that we have changed our version numbering suggested to
comply with Maven scheme. This change has been made only at the maven
level, i.e. in the POM file.
I have recently added the following artifacts to maven under this
scheme, which you should now be able to pick-up. This will also be the
same for future releases. Please note the version numbering of the
product itself has not been changed:
9.4.0-8
9.4.0-9
9.5.1-1
Thanks and kind regards,
O'Neil
On 03/06/13 18:29, Markus KARG wrote:
--
O'Neil Delpratt
Software Developer, Saxonica Limited
Email: oneil@saxonica.com oneil@saxonica.com
Tel: +44 118 946 5894
Web: http://www.saxonica.com
Saxonica Community Site: http://dev.saxonica.com Saxonica Bug tracking
System: https://saxonica.plan.io/
Related
Feature Requests: #23