[
https://issues.jboss.org/browse/SRAMP-412?page=com.atlassian.jira.plugin....
]
Eric Wittmann commented on SRAMP-412:
-------------------------------------
One really important aspect to this is that the Fuse versions of the WARs are produced by
overlay modules. The configuration of the war plugin for these modules manually does the
manifest.mf manipulations to turn the WARs into bundles. This includes putting the
appropriate WEB-INF/lib/*.jar files into the bundle classpath. Unfortunately this is done
in a rather fragile way, since the JARs have version numbers attached. It would sure be
nice to make this more automated (e.g. discover the JARs in there and automatically add
them to the bundle classpath, excluding JARs not being included in the final WAR).
Use the maven-bundle-plugin appropriately to support OSGi for WAR
projects
--------------------------------------------------------------------------
Key: SRAMP-412
URL:
https://issues.jboss.org/browse/SRAMP-412
Project: S-RAMP
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Eric Wittmann
Assignee: Brett Meyer
Fix For: 0.5.0 - API Management
I was never able to get the maven-bundle-plugin working with the WAR modules, perhaps
because they are overlays, perhaps because I was being stupid. In any case, we *really*
should try to get that plugin working to make maintenance of the fuse version more
manageable.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)