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.
Add a similar graphical view of the config file (pom.xml, settings.xml) like it is already available in web.xml. So instead of having to know all the details of how the xml has to look like. I just enter the properties in the UI.
I'm not sure if full fledged visual pom editor is possible for 7.0. I'm not even sure it's the most effective way to help with pom file editing. I'd rather work on editor related items, like hints, code generators (Insert code... action) and so on. A sort of task oriented UI, rather than a flat 1:1 mapping of UI fields to pom elements.
Well I agree that just creating a frontend for an xml file might only be little help for the developer. The challenge is to create a ui that will reveal the full power of the maven pom file. Just having the xml in front of my eyes does not tell me anything of what is possible. The UI should definately be a helper to see what is possible and by 'click and add' do the xml for me without having to search in the depth of the xml structure, which only a few maven geeks understand and know anyway. IMHO .) There should be views for a quick entry for newbies, to configure the most important things without having to know any special naming conventions. .) There should be additional views for even advanced users that would take certain maven-plugin functionality into account, which I can configure easily (task oriented), without having to hunt for information on the internet. .) There may even be taskoriented support for settings.xml, profiles.xml, where I can add eg netbeans specific settings just by clicking eg: special feature 1: .) application scope (settings.xml) .) project scope (profiles.xml) .) in pom.xml See for example the geniously (is this a word :)) simple ui of the netbeans profiler. You choose the task and apply your settings and then start - This might be one way to create a UI. Or just have different categories in one UI like in the web.xml view where I can add settings and the netbeans does the rest for me: Eg. .) Dependency management might be the easiest task, with support for maven repository explorer. |Add Dependency...| -> popup -> maven repository -> search and choose -> |finish| .) also other simple settings that are currently not available as gui, for scm, issuemanagement, developer, contributer, parent-pom support, a view for dependency-analyze/tree .) important esp for beginners would be an easy support for the release plugin .) Advanced tasks for maven-plugins like checkstyle, surefire, maven-source-plugin These are just some ideas. There could also be a addon support in netbeans-maven-support for additional UI's for people who would like to create helpers for that reason. Together with a tutorial how to create such an addon you could concentrate on the basic functionality and the community could create additional UI's to the netbeans-maven support.
*** Issue 154461 has been marked as a duplicate of this issue. ***
*** Issue 154463 has been marked as a duplicate of this issue. ***
FYI: I've tried to write some domain specific code generators (and learn Scala in the process) for tasks like: 1. configure maven site and some basic report plugins 2. enable scala or groovy language in maven project 3. add profile for integration with javarebel. All of these have 1. a Code generator accessible through the Alt-Insert keybinding 2. are included in the generators panel in projetc customizer. See http://kenai.com/projects/nb-maven-generators/
*** Issue 169845 has been marked as a duplicate of this issue. ***
*** Bug 188623 has been marked as a duplicate of this bug. ***
+1 Also have a look at the persistence.xml editor of NetBeans or the POM editor of Eclipse for some inspiration.
Reassigning to default owner.
I have no plans to implement any GUI of this kind. POMs are rather open-ended, and configuration for particular plugins is generally given as XML fragments on various web sites; would prefer to spend any available time on improving code completion.