ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J.C. Hamlin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IVYDE-311) IvyDE does not allow setting of Ivy Home or honor setting of IVY_HOME environment variable
Date Wed, 27 Jun 2012 22:04:42 GMT

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

J.C. Hamlin updated IVYDE-311:
------------------------------

    Description: 
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).

  was: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).

    
> IvyDE does not allow setting of Ivy Home or honor setting of IVY_HOME environment variable
> ------------------------------------------------------------------------------------------
>
>                 Key: IVYDE-311
>                 URL: https://issues.apache.org/jira/browse/IVYDE-311
>             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
>            Priority: Minor
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message