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.
When you have e.g. <profile> <id>netbeans-ide</id> <activation> <activeByDefault>true</activeByDefault> </activation> <properties> <netbeans.installation>...</netbeans.installation> </properties> </profile> in settings.xml, this is basically a permanent definition for Maven. Yet it clutters Run > Set Project Configuration, even though selecting -Pnetbeans-ide would have no additional effect. Any profiles that are activeByDefault should be excluded from the mapping into generated project configurations. (Ideally the same would be true of any other profiles whose activation evaluates to true already.)
are you positive that activeByDefault is always enabled? AFAIK the definition is/was somewhat more fluent. The profile was activated unless some other profile was activated explicitly.
I am not sure offhand is that is true or not. Either way, it still makes no sense to define a profile for e.g. 'netbeans-ide', since -Pnetbeans-ide should behave the same as not setting any -P at all, i.e. the default configuration.
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