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 we open a Maven web application, NetBean recognize a Web Application but - we can't use the Visual Web Pack to open/modify our JSF, - we can't create new Visual Web JSF Page : we have this message "Visual Web items cannot be created because the target project does not support Auxiliary Configuration for saving project properties." and the finish button is disabled. [perhaps we can find a way to force the JSP edition in a Visual Web Editor window]
possibly related to what we discussed at http://www.netbeans.org/issues/show_bug.cgi?id=113284, needs changes both in visual web and maven support. not sure it's a defect, it was never planned for 6.0 AFAIK.
If I'm correct, Visual Web needs support to write couple of Auxillary information in to the project metadata (project.xml) like package name, and component default theme name etc. With out them the components in the designer can not be rendered. Since Maven project does not support adding these Auxillary information. This is a relic from Creator time. Probably we will get rid of these in future release by modifying the Visual Web Architecture itself.
As you already seen "Visual Web items cannot be created because the target project does not support Auxiliary Configuration for saving project properties." The non-support feature is well informed. It's not a bug, visual web does not have enough API to support this feature yet for NetBeans 6.0 plan.
The ideal and standard solution for this kind of integration would be to define an Interface let's say VisualWebModuleImplementation that each project type could place into the project's lookup. The visual web integration would then query the project for this interface whenever needed by the UI. it could look like this: interface VisualWebModuleImplementation { String getCurrentJSFScheme(); String getJSFBeanPackage(); String getJSFProjectVersion(); String getJSFStartPage(); } Also possibly with the relevant setter methods. Maven support is free to implement this interface without the need to add AuxiliaryConfiguration to the project. As I already mentioned in issue 113284, the only item where I see more work coming is the jsf.project.libraries.dir property. It makes no sense for maven-based projects, which store all relevant dependency information in the pom.xml file and the binaries are stored in the local and remote repositories. An arbitrary folder with some binaries is non-supported feat in Maven. BTW are there any special ant steps when building an applicationw ith visual web in it?
Will discuss this future feature in issue#113284. *** This issue has been marked as a duplicate of 113284 ***