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.
Created attachment 138344 [details] Initial draft of the maven.web module I am thinking it may be useful to separate a basic maven.web module from the maven.j2ee module. The maven.web module would provide baselevel support for "web applications", which may not necessarily need to be JavaEE-based. This would benefit some kinds of projects such as: - OSGi-based web applications, which do have a docbase and rely on Java EE APIs, but are packaged as OSGi bundles rather than war files. - Applications that use the experimental Knockout4Java framework - "Containerless" web applications, see issue 233476 for previous discussion The idea is that maven.web would not depend on any Java EE APIs, and could be in a lower cluster than enterprise. It could e.g. be an eager module in the java cluster, that would also depend on the webcommon cluster, which would be useful e.g. for Knockout4Java, as Knockout4Java support would not need to depend on the enterprise cluster. I am attaching a very rough and incomplete patch which moves some classes from maven.j2ee to maven.web, just to illustrate this idea. The patch is compilable, but I did not try to run it.
Interesting idea. If there is a real use case that would benefit from it I can do it. Is there any time-pressure or do we want to target it to the NB 8.0?
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