[jboss-osgi-issues] [JBoss JIRA] (JBOSGI-585) Separate maven project.version from bundle.version and package version
Thomas Diesler (JIRA)
jira-events at lists.jboss.org
Fri Jul 5 03:35:22 EDT 2013
[ https://issues.jboss.org/browse/JBOSGI-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Diesler updated JBOSGI-585:
----------------------------------
Labels: repository (was: )
> Separate maven project.version from bundle.version and package version
> ----------------------------------------------------------------------
>
> Key: JBOSGI-585
> URL: https://issues.jboss.org/browse/JBOSGI-585
> Project: JBoss OSGi
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Distribution, Repository
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Labels: repository
> Fix For: JBossOSGi 2.0.0
>
>
> We have a requirement to suffix final project versions with ".Final". To use this suffix in OSGi manifest headers changes the semantic meaning because 2.0.0.Final < 2.0.0. Hence a requirement of [2.0,3.0) would not include 2.0.0.Final.
> Unless the JBoss version scheme changes we need to deal with this internally. I suggest to generate a maven property that has the suffix removed and use that instead of ${project.version}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-osgi-issues
mailing list