[
https://jira.jboss.org/jira/browse/DNA-373?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-373:
-----------------------------------
One way to do this is (supposedly) as simple as:
<plugins>
<plugin>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifestFile>
${project.build.outputDirectory}/META-INF/MANIFEST.MF
</manifestFile>
</archive>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>2.0.1</version>
<executions>
<execution>
<id>bundle-manifest</id>
<phase>process-classes</phase>
<goals>
<goal>manifest</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
Provide OSGi information in archives (via META-INF/MANIFEST.MF
files)
---------------------------------------------------------------------
Key: DNA-373
URL:
https://jira.jboss.org/jira/browse/DNA-373
Project: DNA
Issue Type: Feature Request
Components: Development Environment, Documentation, Tools
Reporter: Randall Hauch
Priority: Minor
Fix For: Future Releases
If the JBoss DNA JAR files each included a META-INF/MANIFEST.MF file, our existing JARs
could be used as OSGi bundles within an OSGi class loader environment (for example within
Eclipse), while they continue to work outside of an OSGI environment.
Another option is to create a single OSGi bundle containing the top-level archives and
OSGi bundles for each of our extensions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira