[
https://issues.apache.org/jira/browse/IVYDE-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xavier Hanin resolved IVYDE-67.
-------------------------------
Resolution: Fixed
I've migrated plugin metadata format to OSGi and now use an OSGi dependency on
Ivy rather than packaging it in the plugin bundle.
> Use Ivy Bundle instead of packaging ivy.jar in IvyDE bundle
> -----------------------------------------------------------
>
> Key: IVYDE-67
> URL: https://issues.apache.org/jira/browse/IVYDE-67
> Project: IvyDE
> Issue Type: Improvement
> Affects Versions: 1.1.0, 1.2.0
> Reporter: Xavier Hanin
> Assignee: Xavier Hanin
> Fix For: 1.3.0
>
>
> Currently IvyDE packages ivy.jar to get access to Ivy classes, meaning that
> IvyDE versions are closely related to Ivy versions. In some cases it would be
> useful to upgrade the version of Ivy used without changing the version of
> IvyDE (as long as they are compatible).
> Since Ivy is now provided as an OSGi bundle, this could easily be achieved by
> using an OSGi dependency from IvyDE bundle to Ivy bundle, taking advantage of
> OSGi runtime dependencies resolution feature.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
