Hi Stevo,
yes, sounds reasonable. We will have a look into this once you raise a
Jira issue so that it does not get lost .. ;-).
Those $VERSION$ tags somehow look like they are a left-over from the old
Ant build .....
Cheers
Werner Guttmann
On 26.09.2011 16:06, Stevo Slavić wrote:
Hello Castor developers,
It's not first time that the version info in
org.exolab.castor.util.Version is out of sync with actual version (
see
https://svn.codehaus.org/castor/castor/tags/castor-1.3.2/xml/src/main/java/org/exolab/castor/util/Version.java
)
Maven seems to be configured to generate MANIFEST.MF for castor-xml
jar, but wrongly (e.g. MANIFEST.MF for 1.3.2 contains
"Implementation-Version: $VERSION$$RELEASE$")
Assuming that jar plugin gets configured to properly generate
MANIFEST.MF, and include version info there by using/referencing
project.version from pom.xml, IMO it would be DRY solution for
org.exolab.castor.util.Version to read (& cache) version info from
MANIFEST.MF
One of the obstacles would be to read MANIFEST.MF from jar where
org.exolab.castor.util.Version is packaged in. Following stackoverflow
question/topic has some answers:
http://stackoverflow.com/questions/1272648/reading-my-own-jars-manifest
Regards,
Stevo.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
