[jboss-jira] [JBoss JIRA] (JBEE-67) Please make jboss-transactions-api JAR an OSGi bundle.
Paul Gier (JIRA)
jira-events at lists.jboss.org
Thu Mar 8 16:31:37 EST 2012
[ https://issues.jboss.org/browse/JBEE-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier resolved JBEE-67.
---------------------------
Resolution: Done
I decided to keep the current configuration which uses the "manifest" goal of the bundle plugin to generate the manifest which is then picked up by the jar plugin. I prefer this one instead of using the "bundle" packaging, because the jar manifest configuration is automatically merged with the OSGi config.
Also, the using the "bundle" packaging and lifecycle with the 2.3.5 version of bundle plugin seems to disable the generation of attached source jar configured in the jboss-parent pom. However, this seems to be fixed if we update to 2.3.7 of the bundle plugin.
> Please make jboss-transactions-api JAR an OSGi bundle.
> ------------------------------------------------------
>
> Key: JBEE-67
> URL: https://issues.jboss.org/browse/JBEE-67
> Project: JBoss JavaEE Spec APIs
> Issue Type: Task
> Components: jboss-transaction-api
> Affects Versions: 1.0.1.GA-transaction-api
> Reporter: Trustin Lee
> Assignee: Paul Gier
> Priority: Trivial
> Fix For: JavaEE 6 Spec APIs 3.0.0
>
>
> To make Infinispan run on an OSGi container, all its required dependencies need to become an OSGi bundle. jboss-transaction-api is one of them since Infinispan's core is coupled with JTA.
--
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
More information about the jboss-jira
mailing list