[
https://issues.apache.org/jira/browse/IVY-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560446#action_12560446
]
Xavier Hanin commented on IVY-706:
----------------------------------
Mmm, I'm not sure how to deal with that. Ivy is now packaged as an OSGi bundle,
meaning that the jar provided and used by many users outside any OSGi runtime.
In this jar, we cannot afford packaging the dependencies inside the bundle/jar
as OSGi allows to.
Now in an OSGi environment like eclipse equinox, the dependencies are
missing... is it a problem? I'd say it follows OSGi philosophy as I understand
it: the Ivy bundle declares dependencies on a set of packages using the
Import-Package directive, but specifying them as optional. And this is the
case, Ivy can run without any dependency. So if you need one of these
dependencies in an OSGi environment you need to provide them as OSGi bundles
too.
Now comes the IvyDE case. To be simple to use, I guess we should provide an
update site with all the necessary bundles: Ivy, IvyDE and also optional
dependencies as OSGi bundles. We should be able to find some of them if not all
in the OSGi community, maybe from Oscar or equinox.
Hence I'm in favor of closing this bug as Invalid. WDYT?
> The bundle packaging of Ivy is incorrect
> ----------------------------------------
>
> Key: IVY-706
> URL: https://issues.apache.org/jira/browse/IVY-706
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-beta-2
> Reporter: Nicolas Lalevée
> Priority: Minor
> Attachments: IVY-706-r612799.patch
>
>
> Ivy has recently been packaged as an OSGI bundle by adding a MANIFEST.MF. But
> it is not correct since the runtime jars are not declared in the manifest.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
