On 2007-08-03 01:32:06 +0400, Travis Reeder <treeder@gmail.com> said:
So you don't need to edit it everytime you update Idea.
This file is read by Exe4j launcher and it doesn't have an option to specify it's location(s). The same story goes for MacOS. Info.plist file is being read by JavaApplicationStub, which expects VM parameters at well known place.
On Fri, 03 Aug 2007 00:08:33 +0400, Maxim Shafirov <max@jetbrains.com> wrote:
On 2007-08-03 01:32:06 +0400, Travis Reeder <treeder@gmail.com> said:
> >> So you don't need to edit it everytime you update Idea. >
This file is read by Exe4j launcher and it doesn't have an option to specify it's location(s). The same story goes for MacOS. Info.plist file is being read by JavaApplicationStub, which expects VM parameters at well known place.
+1
It's a pain to remember to change it every time.
And the equivalent for Mac, por favor.
--Dave Griffith
Much Agreed! I often forget and then wonder why my new version is not performing well.
How about read-only file attribute?
On 2007-08-03 01:32:06 +0400, Travis Reeder <treeder@gmail.com> said:
This file is read by Exe4j launcher and it doesn't have an option to
specify it's location(s).
The same story goes for MacOS. Info.plist file is being read by
JavaApplicationStub, which expects VM parameters at well known place.
On Fri, 03 Aug 2007 00:08:33 +0400, Maxim Shafirov <max@jetbrains.com>
wrote:
>
>> So you don't need to edit it everytime you update Idea.
>
>
But it's possible to patch idea.sh!