This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 205735 - Maven options no longer contains repository settings
Summary: Maven options no longer contains repository settings
Status: RESOLVED WONTFIX
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 7.1
Hardware: PC Linux
: P3 normal (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-30 17:56 UTC by massimo
Modified: 2011-12-27 21:59 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description massimo 2011-11-30 17:56:45 UTC 
Product Version = NetBeans IDE 7.1 RC1 (Build 201111242103)
Operating System = Linux version 2.6.32-35-generic running on amd64
Java; VM; Vendor = 1.6.0_25
Runtime = Java HotSpot(TM) 64-Bit Server VM 20.0-b11

Maven Options no longer contains repository settings: how do you now tell the IDE that your local repository is not under the default location $HOME/.me/repository, but somewhere else?

Had to work that around at the Maven installation level, but used to be handy to do this within the Tools->Options->Misc->Maven window.
Was that feature removed on purpose, and if so, what is the workaround now? Any specific instructions? That window does not say.
Comment 1 Jesse Glick 2011-12-01 15:00:00 UTC 
(In reply to comment #0)
> how do you now tell the
> IDE that your local repository is not under the default location
> $HOME/.m2/repository, but somewhere else?

The same way you tell Maven itself: <localRepository> in ~/.m2/settings.xml or $MAVEN_HOME/conf/settings.xml.

> Was that feature removed on purpose

Yes. The IDE now reads global settings from the selected Maven installation, which it did not use to do, so overrides for individual features are no longer necessary.
Comment 2 massimo 2011-12-27 20:32:47 UTC 
Issue seems related to bug 205735 and bug 553750.
Comment 3 massimo 2011-12-27 20:37:30 UTC 
Sorry, wrong number, trying again:
Issue seems related to bug 206750 and exception 553750.
Reopening in case this mattered, as it has a cascade effect on 206750 and 553750.
Please close again if not applicable in case you will be looking for a different fix: just reopening to grab attention in regards to 553750 and 206750.
Comment 4 Jesse Glick 2011-12-27 21:59:27 UTC 
This issue is WONTFIX regardless of other issues.