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.
This is analogous to enhancement 222236, which asks for HTML5 functionality in Ant projects. Project Easel functionality (most importantly browser integration, JavaScript debugging and visual CSS editing) needs to also be available in Maven web projects. This support should be consistent with support in Ant projects (issue 222236).
Due to the fact that this should be implemented in trunk, I'm not sure if it's a good idea to do it now. I have made some changes on javaee7 branch in customizer UI and as far as I understand this some UI changes has to be made to accomplish this feature. This will surely result in conflicts during the branch merging (and they won't be easy to solve, I have also refactored quite a lot of code on the branch --> see web-main #89d0da06af1b for better picture).. would it be good enough to implement this once the javaee7 branch will be merged in trunk?
Ok, I understand your concern. I am uncomfortable leaving this until mid-April, so the two options I can think of are: - Implement this functionality in the EE 7 branch (and leave it disabled by default) or in a separate branch on top of the EE 7 branch. But this has the problem that the implementation may depend on some changes that David made in trunk recently - Merge javaee7 branch to trunk now and then again at the end of the 7.3.1 development cycle (and possibly several times in between) What do you think?
(In reply to comment #2) > Ok, I understand your concern. I am uncomfortable leaving this until mid-April, > so the two options I can think of are: > - Implement this functionality in the EE 7 branch (and leave it disabled by > default) or in a separate branch on top of the EE 7 branch. But this has the > problem that the implementation may depend on some changes that David made in > trunk recently > - Merge javaee7 branch to trunk now and then again at the end of the 7.3.1 > development cycle (and possibly several times in between) > > What do you think? Option one sounds impossible with respect to some API dependencies. Option two sounds good to me. Maybe it would be even better then wait for next three months and hope that we will be able to merge everything back to trunk.
CCing few others to get wider agreement or opposite opinion (please see comment 2)
In my opinion it's good to have javaee7 merge into default from time to time even if we'll continue to use javaee7 also. One more point are possible merge conflicts after collecting a lot of difference between default/javaee7 with parallel development.
First part fixed in: web-main #49b2bb0da334 web-main #e1ef0115c8b6 ..deploy on save support is still missing, but the rest should be done. I'm on it..
Integrated into 'main-golden', will be available in build *201302202300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/49b2bb0da334 User: Martin Janicek <mjanicek@netbeans.org> Log: #225786 part 1 - Browser selection in project customizer
Deploy on save feature added in: web-main #eb570c090177 AFAIK this was the last item --> Closing the ticket
Integrated into 'main-golden', will be available in build *201303122300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/eb570c090177 User: Martin Janicek <mjanicek@netbeans.org> Log: #225786 - Support for HTML5 features (Project Easel) in Maven Web projects