[
https://issues.jboss.org/browse/AS7-6211?page=com.atlassian.jira.plugin.s...
]
jarkko rantavuori updated AS7-6211:
-----------------------------------
Steps to Reproduce:
- download and unzip 7.2 snapshot from
https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/lastSuccessfulBuild/...
- add an admin user with bin\add-user
- start the server with bin\standalone
- view the admin console at
http://localhost:9990/console/App.html#osgi-runtime, logging
in with admin user
was:
- download and unzip 7.2 snapshot
- add an admin user with bin\add-user
- start the server with bin\standalone
- view the admin console at
http://localhost:9990/console/App.html#osgi-runtime, logging
in with admin user
JBoss OSGi bundles show version 0.0.0 in AS 7.2.0.Alpha1
--------------------------------------------------------
Key: AS7-6211
URL:
https://issues.jboss.org/browse/AS7-6211
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.2.0.Alpha1
Environment: Windows 7
Reporter: jarkko rantavuori
Assignee: Thomas Diesler
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
--
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