Copingg jars to the system directory.

The 668 'release notes' say:

'Option not to copy jars into the system directory.
Use -Didea.jars.nocopy=true in the command line'

OK ..

When would we want to do this ?
When would we not want to do this ?
Why is this done at all ?


1 comment
Comment actions Permalink

Due to the way Java works with jar files they get locked when the program
opens them for reading. Because we have been receiving a lot of complaints
about IDEA locking the archives, the default behavior is to cache the files
by copying them to the system directory and updating when the original copy
has changed (e.g. during an Ant build). If you are sure that you can live
with IDEA locking the files, you may turn the caching (which consumes quite
some disk space itself) by using the mentioned option.

Eugene Belyaev
JetBrains, Inc

"Lenny Karpel" <lkarpel@eloquent.com> wrote in message
news:appfpn$8p4$1@is.intellij.net...

The 668 'release notes' say:

>

'Option not to copy jars into the system directory.
Use -Didea.jars.nocopy=true in the command line'

>

OK ..

>

When would we want to do this ?
When would we not want to do this ?
Why is this done at all ?

>
>


0

Please sign in to leave a comment.