|
History
| Log In
|
|
|
|
Hi Milos,
Setting the MAVEN_HOME env. variable in my $HOME/.profile does not set it for NB. It must be explicitly set in the NB startup script somewhere for OS X. You are correct that only MAVEN_HOME is needed from within the NB IDE. It is not necessary to modify PATH. From the command line (Terminal on OS X), all the usual Unix rules apply. If the maven script is not already in the path, then PATH must be modified. As expected, MAVEN_HOME must be exported in .profile or by a script. Bottom line - OS X can look like Unix and walk like Unix, but any GUI program launched from the Finder skips any benefit from the user login script. Travis Here is a far more elegant solution provided by Thomas Much on the Apple java-dev list.
"Download the preference pane "RCEnvironment" (http://www.rubicode.com/Software/RCEnvironment/ The description of the tool says "RCEnvironment is a preference pane for MacOS X 10.1 or higher that allows editing of a user's ~/.MacOSX/environment.plist file. This file provides environment variable capability similar to Windows' Environment User Variables." Travis ok, thanks for the explanation. I wil add it as an entry to the FAQ.
ok, I've updated the faq and added entry about macosx install.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Closed
Minor
Improvement for docs on mevenide-NB install on OS X
I think everyone who wants to run maven (either inside or outside the IDE) has to setup the MAVEN_HOME env. variable.
The PATH variable update should not be necessary IMHO, mevenide finds the executable based on the MAVEN_HOME variable. Or didn't it work for you?