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 255606 - Allow per-project settings (i.e. which warnings are enabled) to be shared across teams via source control
Summary: Allow per-project settings (i.e. which warnings are enabled) to be shared acr...
Status: NEW
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 8.1
Hardware: PC Mac OS X
: P3 normal (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-28 13:21 UTC by pdurbin
Modified: 2015-10-09 18:54 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
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 pdurbin 2015-09-28 13:21:58 UTC 
As discussed with Geertjan Wielenga at https://javabot.evanchooly.com/logs/%23netbeans/2015-09-28 it would be very nice if I could enable "Standard Javac Warnings" for one of the projects I edit with NetBeans and save that setting to a file that I check into the projects source tree so that other developers on the team could pull the latest code and have their installation of NetBeans pick up the new setting about which warnings are now enabled for that project project.

Currently, you can export your settings and send a zip file to a team member but the settings are global. Per-project settings would be much preferred. It sounds like a possible step along the way, per Geertjan, would be making inspections exportable. In the chat above he said, "Well, more generally, would be nice if the inspections (whether javac warnings or whatever else) could be exported/imported in the same way as settings in the Options window." I've written this issue more generally, however, to capture the user story of keeping development teams on the same page with regard to which warnings should be enabled on a per-project basis.
Comment 1 Jiri Kovalsky 2015-10-02 09:27:31 UTC 
Reassigned for further evaluation.
Comment 2 Theofanis Oikonomou 2015-10-02 09:41:15 UTC 
hmmm my first impression is that this is project infra related. Re-assigning for evaluation. Thank you
Comment 3 pdurbin 2015-10-09 13:05:41 UTC 
I see the "Component" was changed to "Ant Project" but I almost never use Ant myself. Mostly I use Maven.
Comment 4 msanghvi 2015-10-09 18:54:48 UTC 
I work with multiple teams, across product and project lines, in my capacity as a release/build engineer.  When I import projects into Netbeans, I have no way
to tell Netbeans that for Project A, I want you to use projectA.settings.xml located at /path/to/some/location; for Project B use projectB.settings.xml located at /some/other/path/to/settings/file.  

Currently I can only specify this in the global settings.  I know IntelliJ provides a project level setting which over-rides the global setting for such things.  I believe Eclipse does too.  It would be awesome to have this in Netbeans too.  

This seems like the right bug to comment on, but if it is not, do excuse this and let me know what I need to do to get the right people to notice this.