[jboss-osgi-issues] [JBoss JIRA] (JBOSGI-677) Some javax.* bundles show version 0.0.0 in AS7
Thomas Diesler (JIRA)
jira-events at lists.jboss.org
Fri Jul 5 01:01:37 EDT 2013
[ https://issues.jboss.org/browse/JBOSGI-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Diesler moved WFLY-163 to JBOSGI-677:
--------------------------------------------
Project: JBoss OSGi (was: WildFly)
Key: JBOSGI-677 (was: WFLY-163)
Workflow: jira (was: GIT Pull Request workflow )
Component/s: (was: OSGi)
> Some javax.* bundles show version 0.0.0 in AS7
> ----------------------------------------------
>
> Key: JBOSGI-677
> URL: https://issues.jboss.org/browse/JBOSGI-677
> Project: JBoss OSGi
> Issue Type: Bug
> Reporter: Thomas Diesler
>
> Some javax bundles that we configure by default do not show valid bundle version info
> javax.jws.api:0.0.0
> javax.ws.rs.api:0.0.0
> The javax.persistence.api has its metadata defined in jbosgi-xservice.properties like this
> {code}
> Bundle-SymbolicName: hibernate-jpa-2.0-api
> Bundle-Version: 1.0.1.Final
> Export-Package: javax.persistence.spi;version="2.0.0",javax.persistence.criteria;version="2.0.0",javax.persistence;version="2.0.0",javax.persistence.metamodel;version="2.0.0"
> {code}
> This should be replaced by metadata coming from the artefacts manifest.
> Generally, all javax api artefacts should have valid OSGi metadata
--
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