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.
If I have a Git-controlled Maven project and select “Keep private to this IDE instance” in the “Add configuration” dialog, and select a main class and args in this configuration, NetBeans nonetheless creates two files in my project directory: 1. nb-configuration.xml, even though <configurations/> is empty! This file marks the project as modified in the Projects tab. 2. nbactions-foo.xml, which appears as ignored (grey) in the Projects tab, but is still considered an “untracked file” by Git, i.e. it is not added to .gitignore. When I click the checkbox in question I expect the IDE to not touch my version-controlled sources; it should keep all the information it needs in the user directory somewhere.
partly solved by issue 224450, the rest is here: http://hg.netbeans.org/core-main/rev/f0077e617638
OK that should solve #1; are you intentionally punting on #2?
the nbactions file doesn't appear anymore? so it's correctly only created when shared configuration is created and then it's ok to be not-ignored?
I am saying that f0077e617638 should correctly suppress an empty nb-configuration.xml. The complaint remains that when I create a “private” run configuration and bind actions in it, this nbactions-*.xml configuration is stored in ${basedir} rather than being kept somehow in ${netbeans.user}. It is not offered for commit by the IDE’s own SCM actions, because it is considered ignorable, but still pollutes the project from the perspective of command-line SCM operations.
Integrated into 'main-golden', will be available in build *201302132300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/f0077e617638 User: Milos Kleint <mkleint@netbeans.org> Log: #226017 don't create new file when no configs are specified. (eg. when creating a private configuration)
cachedirectoryprovider's location would be a possibility, however the main drawback there is that on upgrading the IDE, the customizations are lost. Or at least I don't know of a way of telling the import to include such files/folders from previous version of the IDE.
Does adding an OptionsExport entry not suffice?
(In reply to comment #7) > Does adding an OptionsExport entry not suffice? last time I checked it only handles stuff on the system file system. no way to import/export stuff from cache directory. I wanted to use it to move the maven indexes folders over to the new cache directory to save people from re-downloading central index
btw ant projects' private configuration is also stored in project space (nbproject/private)
Which was a mistake.
I don't want to dismiss the idea entirely, not a bug though. The current scope is "per user" you are suggesting to change that per "IDE version instance" with import possibilities, changing to enhancement
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss