[
https://issues.jboss.org/browse/AS7-6216?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler updated AS7-6216:
--------------------------------
Description:
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 valid OSGi metadata
was:
JBoss internal OSGi bundles seem to always report bundle version as 0.0.0. Examples from
the admin console:
javax.annotation.api:0.0.0
javax.ejb.api:0.0.0
javax.interceptor.api:0.0.0
javax.jms.api:0.0.0
javax.jws.api:0.0.0
javax.management.j2ee.api:0.0.0
javax.persistence.api:0.0.0
javax.servlet.api:0.0.0
javax.transaction.api:0.0.0
javax.ws.rs.api:0.0.0
javax.xml.bind.api:0.0.0
javax.xml.ws.api:0.0.0
org.jboss.as.osgi.http:0.0.0
Some javax.* bundles show version 0.0.0 in AS7
----------------------------------------------
Key: AS7-6216
URL:
https://issues.jboss.org/browse/AS7-6216
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.2.0.Alpha1
Environment: Windows 7
Reporter: jarkko rantavuori
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
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 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