Permanently setting idea.exe.vmoptions

idea.exe.vmoptions gets overwritten everytime I reinstall a beta. Does IDEA
support putting this file in the system folder or somewhere so that it's
permanent?

--
Jordan Zimmerman
Senior Software Architect
SHOP.COM
http://www.shop.com


12 comments

Personally, I never install an EAP build "over top" of another. It makes it
easier to back out if needed. I just wrote a little batch file that renames
the directory of older build, unzips new build to the "pre rename"
directory, copies relevant files (idea.exe.vmoptions, idea.properties,
etc...) from "renamed directory" to "pre rename" directory (creating backups
of the new ones in case something changed).

"Jordan Zimmerman" <jordanz@shop.com> wrote in message
news:e23e5s$t9o$1@is.intellij.net...

idea.exe.vmoptions gets overwritten everytime I reinstall a beta. Does
IDEA support putting this file in the system folder or somewhere so that
it's permanent?

>

--
Jordan Zimmerman
Senior Software Architect
SHOP.COM
http://www.shop.com

>



0

"Brad L" <no@no.no> wrote in message news:e23elt$uug$1@is.intellij.net...

Personally, I never install an EAP build "over top" of another. It makes
it easier to back out if needed.


I don't insall over either. I use the .exe as the JAR stopped working for me
a while ago. I guess I could write a script, but it's a pain. Also, IntelliJ
should consider this a feature need. In the non-beta world, users don't want
to lose their VM settings when upgrading.

-Jordan


0

What I do is make the idea.exe.vmoptions and idea.properties to read only and when I unzip the file it asks to overwrite and I say no.

Hope the same works for *.exe installation.

Regards,
--Venkat.

0

I've been bitten enough myself to finally do something about this, particularly since I'm stuck in a fairly boring meeting. I've build a teeny, tiny plugin called VMOptions, which allows you to edit the idea.exe.vmoptions from a Settings panel, and stores the information in the system directory. New installs (including overwrites) will just need to restart IDEA to have their previous VM options restored.

One class, one form, one annoyance solved.

Yeah, it's a cheesy hack, but it's my cheesy hack. QA'ing now, should be up on the plugin site shortly.

--Dave

0

VMOptions should be up, although the plugin manager seems to be having trouble getting downloads.

--Dave Griffith

0

Nice, but under Linux the file is idea.vmoptions, not idea.exe.vmoptions
Not sure about OS X.
R

0

Cool. Version 1.0.1 is up and should fix it for Linux. If someone tells me the appropriate file location for OSX I'll fix it for 1.0.2.

Oh, yeah. Source is included in the download, Apache 2.0 license, feel free to play with it within those limits, yadda, yadda, yadda.

--Dave Griffith

0

Robert Gibson wrote:

Nice, but under Linux the file is idea.vmoptions, not idea.exe.vmoptions


<http://www.jetbrains.net/jira/browse/IDEADEV-5525> means you can now
use the IDEA_VM_OPTIONS environment variable to name the file from which
you'd like VM options to be read (and that file needn't be called
idea.vmoptions).

--
Mark Scott
mark@codebrewer.com

0

"Mark Scott" <intellij_news@codebrewer.com> wrote in message
news:bogkh3-j3d.ln1@news.codebrewer.com...

Robert Gibson wrote:

>
>> Nice, but under Linux the file is idea.vmoptions, not idea.exe.vmoptions
>

<http://www.jetbrains.net/jira/browse/IDEADEV-5525> means you can now
use the IDEA_VM_OPTIONS environment variable to name the file from which
you'd like VM options to be read (and that file needn't be called
idea.vmoptions).


That's a nice feature, but it doesn't seem to work on Windows.

-Jordan


0

Jordan Zimmerman wrote:


That's a nice feature, but it doesn't seem to work on Windows.


You're right, and I meant to say as much. I admit to being selfish and
only supplying a patch for the Unix launch script. Sorry about that ;)

--
Mark Scott
mark@codebrewer.com

0

Please sign in to leave a comment.