[
https://issues.jboss.org/browse/AS7-2060?page=com.atlassian.jira.plugin.s...
]
Aaron Whiteside commented on AS7-2060:
--------------------------------------
I've taken a look at the pull request for AS7-1601 and can only see a reference to a
few javax.* packages in the javaee.api module.
{code}
Bundle-SymbolicName: javaee.api
Export-Package:
javax.inject,javax.servlet;version=3.0,javax.servlet.annotation;version=3.0,javax.servlet.descriptor;version=3.0,javax.servlet.http;version=3.0,javax.transaction;version=1.1,javax.transaction.xa;version=1.1
{code}
I don't see how this change or any other change in the pull request will be setting
the version for javax.jms or javax.transaction, javax.validation, javax.ws, javax.inject,
etc, etc the list goes on. All these packages will still be exported with version 0.0.0.
Add correct package version information to packages exported by the
javaee.api module
-------------------------------------------------------------------------------------
Key: AS7-2060
URL:
https://issues.jboss.org/browse/AS7-2060
Project: Application Server 7
Issue Type: Bug
Components: EE, OSGi
Affects Versions: 7.0.2.Final
Reporter: Aaron Whiteside
Assignee: Thomas Diesler
Currently all packages exported by the module javaee.api to OSGi land are exported with
version 0.0.0.
A lot of existing bundles that use classes/packages from javax.* specify a version, which
makes this not work correctly in JBoss 7 AS.
This makes bundles that depend on for example: javax.jms;version=1.1 not work.
The correct version information should be exported by the javaee.api bundle. Because at
the moment it's pretty much useless with the existing libraries/bundles.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira