mevenide

Improvement for docs on mevenide-NB install on OS X

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: mevenide-netbeans
  • Labels:
    None
  • Environment:
    OS = Mac OS X 10.3.5
    NB = 4.0 Beta 1
  • Number of attachments :
    0

Description

Please add to the install documentation for NetBeans that adding the file /etc/netbeans.conf with the content below will add runtime support without modifying the NetBeans file.

The string {your path to maven} will, of course, need to be replaced with the actual path of the reader's install.

#### File contents begins with the next line #####
# /etc/netbeans.conf - additional environment variables for netbeans

MAVEN_HOME=/{your path to maven}/maven-1.0
export MAVEN_HOME

PATH=$PATH:$MAVEN_HOME/bin
export PATH

        1. File contents ends with the line immediately above #####

Travis

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Milos Kleint added a comment -

how is this related to OSX?
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?

Show
Milos Kleint added a comment - how is this related to OSX? 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?
Hide
Permalink
Travis Risner added a comment -

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

Show
Travis Risner added a comment - 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
Hide
Permalink
Travis Risner added a comment -

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

Show
Travis Risner added a comment - 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
Hide
Permalink
Milos Kleint added a comment -

ok, thanks for the explanation. I wil add it as an entry to the FAQ.

Show
Milos Kleint added a comment - ok, thanks for the explanation. I wil add it as an entry to the FAQ.
Hide
Permalink
Milos Kleint added a comment -

ok, I've updated the faq and added entry about macosx install.

Show
Milos Kleint added a comment - ok, I've updated the faq and added entry about macosx install.
Hide
Permalink
Milos Kleint added a comment -

closing

Show
Milos Kleint added a comment - closing

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:

Time Tracking

Estimated:
30m
Original Estimate - 30 minutes
Remaining:
30m
Remaining Estimate - 30 minutes
Logged:
Not Specified
Time Spent - Not Specified
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.