Generate a separate artifact for OSGi bundles.
----------------------------------------------
Key: QI-338
URL: http://issues.ops4j.org/browse/QI-338
Project: Qi4j
Issue Type: Improvement
Reporter: Niclas Hedhman
Assignee: Niclas Hedhman
Many of the dependencies, such as OpenRDF are not 'bundlized', and that makes
deployment to OSGi quite troublesome. It would be good if those dependencies
were embedded and possibly exported by the Qi4j subsystem that uses them. This
would drastically reduce the number of bundles deployed, making each Qi4j
extension and library a self contained unit, and therefor simplify OSGi
deployment drastically.
One option is that we could stick that into the existing jar file, but that
would result in bloated jars for non-OSGi deployments, as these internal jars
are not usable by the JVM itself.
Second option is that we could take the Qi4j jar and the dependent jars and put
those in a 'bundle', which would be directly usable by OSGi, but also useful
for people who take the Qi4j extension, then explodes the Jar into a directory,
which then would contain all they need. Specially useful for people who don't
use Maven nor interested in our SDK.
Third option is to simply create a optimized OSGi bundle, with all Qi4j classes
in the bundle jar but dependents in their own jars embedded in the bundle, i.e.
standard OSGi distribution.
I think that the second option is the most preferred one, and will try to go
for that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev