Community
Participate
Working Groups
Created attachment 213318 [details] Default location when creating a new file When using a Mavenized web project with m2e-wtp, org.eclipse.wst.common.component looks like : <?xml version="1.0" encoding="UTF-8"?> <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="war"> <wb-resource deploy-path="/" source-path="/target/m2e-wtp/web-resources"/> <wb-resource deploy-path="/" source-path="/src/main/webapp" tag="defaultRootSource"/> <wb-resource deploy-path="/WEB-INF/classes" source-path="/src/main/java"/> <wb-resource deploy-path="/WEB-INF/classes" source-path="/src/main/resources"/> <property name="context-root" value="war"/> <property name="java-output-path" value="/war/target/classes"/> </wb-module> </project-modules> If I select the project (or the src/main/webapp folder) and call the "New > HTML File" or "New > JSP file" wizards, the default location is always /target/m2e-wtp/web-resources, which m2e-wtp uses to keep generated files only. I expect the default location to be the folder I selected, if it's listed in the deployment assembly or the one tagged with "defaultRootSource" otherwise. This is pretty annoying actually, when you do demos. Tested in Indigo SR2 and Juno M6.
Created attachment 213874 [details] Patch for New HTML File wizard See patch.txt. This is a patch for New HTML File wizard.
Thank you for the patch, Alexey. While I don't think it's the full solution, it makes for a good starting point.
Thanks for the bug report and the patch. I ended up implementing it a bit differently, included the CSS wizard in the fix, and pushed the changes to R3_4_maintenance and master. http://git.eclipse.org/c/sourceediting/webtools.sourceediting.git/commit/?id=c8c092dd8c2b6f6b54c6d409fed02bcfcd2c057a