You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Nicolas Lalevée (JIRA)" <ji...@apache.org> on 2010/01/09 19:58:54 UTC

[jira] Resolved: (IVYDE-171) Add a separate pluging that adds ivy.jar to the Ant classpath

     [ https://issues.apache.org/jira/browse/IVYDE-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolas Lalevée resolved IVYDE-171.
-----------------------------------

    Resolution: Fixed
      Assignee: Nicolas Lalevée

An new plugin will be available with the next release of Ivy. It will be downloaded along with Ivy itself.

> Add a separate pluging that adds ivy.jar to the Ant classpath
> -------------------------------------------------------------
>
>                 Key: IVYDE-171
>                 URL: https://issues.apache.org/jira/browse/IVYDE-171
>             Project: IvyDE
>          Issue Type: Improvement
>    Affects Versions: 2.0.0.beta1
>            Reporter: Daniel Dekany
>            Assignee: Nicolas Lalevée
>
> You should publish a separate plugin on http://www.apache.org/dist/ant/ivyde/updatesite whose sole purpose is to expose Ivy.jar to Ant under Eclipse. That would prevent the surprises and the ensuing FAQ (why Ivy tasks can't be defined) since most users just check the top-level node of the update site in the Eclipse installer, hence grabbing all the plugins there. Also then users could benefit from the Eclipse plugin installer/updater facility, rather than fiddling with the Any classpath manually.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.