ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <>
Subject [jira] [Commented] (IVYDE-311) IvyDE does not allow setting of Ivy Home or honor setting of IVY_HOME environment variable
Date Mon, 30 Jul 2012 23:52:33 GMT


Nicolas Lalevée commented on IVYDE-311:

I have added a configuration parameter called 'Ivy user dir', configurable at the workspace
level or project by project.
> IvyDE does not allow setting of Ivy Home or honor setting of IVY_HOME environment variable
> ------------------------------------------------------------------------------------------
>                 Key: IVYDE-311
>                 URL:
>             Project: IvyDE
>          Issue Type: Bug
>          Components: ivysettings editor
>    Affects Versions: 2.2.0.beta1
>         Environment: MyEclipse 9.1 64-bit, JDK 1.6.0_31 64-bit, Windows 7 Enterprise
SP1 64-bit
>            Reporter: J.C. Hamlin
>            Assignee: Nicolas Lalevée
>            Priority: Minor
>             Fix For: trunk
> IvyDE does not seem to honor the setting of the environment variable IVY_HOME, nor does
it allow you to configure where you want your Ivy Home to be. It should work like the Ant
plugin does, and allow you to configure, at a workspace level, the location Ivy Home.
> This is important because for many users, the default C:\Users\<username\.ivy2 directory
is not on a fast storage device (like an SSD), and things run *much* faster with the ivy cache
running on an SSD or RAM drive. We are currently using linkd.exe to create an NTFS junction
to the location where we want Ivy Home.
> This however, is also somewhat of a performance hit as going through an NTFS junction
causes some overhead. We can tell, because with a command-line build with IVY_HOME set to
an SSD, it completes 30 seconds faster than with the IVY_HOME unset buy going through the
NTFS junction point (9:30 vs. 10:30).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message