Community
Participate
Working Groups
Build Identifier: WTP 3.2 right now both static and dynamic web projects require a folder in the project, but not the project root itself, to be specified as the "web content folder", internally designated as the "publishing root". This requirement is very artificial. I understand it's set up this way so that project metadata that do not need be published can live outside of the publishing root, however this should be a recommended default, instead of a required configuration. There are legitimate reasons for some projects to use the project root as the publishing root. we should allow that. This means that: - in the facet configuration page, allow project root to be specified as the content folder - in the Deployment Assembly mapping dialog, display the resource tree starting with the project, instead of the webcontent folder - there may be other UI that need to be modified Reproducible: Always
Is Java EE Tools a better "home" for this request?
Yes it should - we'll take a look - I though we did allow this :) (although not recommended because there is no way to configure excluding metadata files etc...)
The two project types do need to be considered... because wst.web projects typically don't use/build java content, this idea makes more sense. But typically Java projects don't ship source, so using the project root might not be practical.
