You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-commits@incubator.apache.org by "Xavier Hanin (JIRA)" <ji...@apache.org> on 2007/04/10 10:18:32 UTC
[jira] Resolved: (IVY-464) OSGIfy ivy artifacts
[ https://issues.apache.org/jira/browse/IVY-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xavier Hanin resolved IVY-464.
------------------------------
Resolution: Fixed
I've integrated your manifest in our build, and tested the resulting jar in knopflerfish, and it seems to work properly (but my test was very basic).
I would appreciate if you have the opportunity to test (run "ant jar" and check the build/artifacts/ivy.jar) and give feedback.
I haven't changed ivy-core.jar, because I don't know if we will keep the packaging as is in the future (that is, for 2.0 release), so I didn't want to spend time for something not really useful IMO.
Thanks a lot for your contribution.
> OSGIfy ivy artifacts
> --------------------
>
> Key: IVY-464
> URL: https://issues.apache.org/jira/browse/IVY-464
> Project: Ivy
> Issue Type: Improvement
> Components: Ant, Core
> Reporter: Costin Leau
> Assigned To: Xavier Hanin
> Fix For: 2.0
>
> Attachments: MANIFEST.MF
>
>
> By adding a few entries to the Ivy manifest, the distribution can be used in OSGi environments/frameworks (such as Spring/OSGi).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.