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

Erik-Berndt Scheper updated IVYDE-122:
--------------------------------------

    Description: 
Currently the build system of IVYDE requires a fixed filename of the ivy jar.  
(org.apache.ivy_cr1.jar). 
If this jar is not available, the build stops with a strange error (such as in 
IVYDE-65).

It would be very nice if 
* The IVYDE build (e.g. ant install-ivy) would support an arbitrary version of 
the ivy jar
* If the jar is not available, a decent error message would be logged
* The build instructions on the wiki 
(http://cwiki.apache.org/IVY/releasing-ivyde.html) were updated to reflect the 
current build procedure



  was:
Currently the build system of IVYDE requires a fixed filename of the ivy jar.  
(org.apache.ivy_cr1.jar). 
If this jar is not available, the build stops with a strange error (such as in 
IVYDE-65).

It would be very nice if 
* The IVYDE build (e.g. ant install-ivy) would support an arbitrary version of 
the ivy jar
* If the jar is not available, a decent error message would be logged




> Support latest dev version of ivy.jar in IVYDE build
> ----------------------------------------------------
>
>                 Key: IVYDE-122
>                 URL: https://issues.apache.org/jira/browse/IVYDE-122
>             Project: IvyDE
>          Issue Type: Improvement
>    Affects Versions: 2.0
>            Reporter: Erik-Berndt Scheper
>             Fix For: 2.0
>
>
> Currently the build system of IVYDE requires a fixed filename of the ivy jar. 
>  (org.apache.ivy_cr1.jar). 
> If this jar is not available, the build stops with a strange error (such as 
> in IVYDE-65).
> It would be very nice if 
> * The IVYDE build (e.g. ant install-ivy) would support an arbitrary version 
> of the ivy jar
> * If the jar is not available, a decent error message would be logged
> * The build instructions on the wiki 
> (http://cwiki.apache.org/IVY/releasing-ivyde.html) were updated to reflect 
> the current build procedure

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

Reply via email to