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.
I do not like very much that the maven home choice is e group project property. I would have really prefer that it will be a project property . But you make me understand in a netcat discussions that It won't be changed. So it will be cool if the jdk choice will also be a group property. Than we will have the possibility to choose one jdk for all projects in a group. Best regards.
technically it's even now possible to share the same jdk setting for multiple projects through the inheritance in pom files. which has a more clearly defined scope than the project group setting. the backend part is fairly clear. project is the ultimate place of decision. If not defined in project, we currently fallback to default jdk but could easily insert a check for project group setting. A bit troubling is the mass change of classpath for all projects (opened or not) when the project group setting changes. it's unclear what sort of side effects we could get from that (red error marks in some projects?) on the UI side of things, I'm unsure what the project group setting would have on project settings and user choices there. Will we ever remove the project setting? like if it matches the project group one?
Possibly duplicate of issue 234324
(In reply to Milos Kleint from comment #1) > technically it's even now possible to share the same jdk setting for > multiple projects through the inheritance in pom files. which has a more > clearly defined scope than the project group setting. > the IDE generated nb-configuration.xml file contains the following text that should help everyone to make a single JDK shared across multiple RELATED projects (same multiproject tree/shared parent). The project group setting is mostly useful for unrelated projects that are part of the group. Please note that while stuff in pom.xml is shared across developers, the project group settings are not and will not (unlike eclipse workspace) <properties xmlns="http://www.netbeans.org/ns/maven-properties-data/1"> <!-- Properties that influence various parts of the IDE, especially code formatting and the like. You can copy and paste the single properties, into the pom.xml file and the IDE will pick them up. That way multiple projects can share the same settings (useful for formatting rules for example). Any value defined here will override the pom.xml file value but is only applicable to the current project. --> <netbeans.hint.jdkPlatform>JDK_1.6</netbeans.hint.jdkPlatform>
I completely totally agree with all your comments and specially with : "Please note that while stuff in pom.xml is shared across developers, the project group settings are not and will not (unlike eclipse workspace)" This is the reason why I do not like the ability to chose maven home in group properties. I still do not understand why maven home can not be a netbeans hint in the nb-configuration.xml project file. But as a end user, I want to be able to chose the jdk home and the maven home at the same place for a same hierarchy of maven projects.
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