Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 355080

Summary:	Should allow project root to be configured as publishing root
Product:	[WebTools] WTP Java EE Tools	Reporter:	Jim Zhang <jzhang>
Component:	jst.j2ee	Assignee:	Roberto Sanchez Herrera <shr31223>
Status:	NEW ---	QA Contact:	Chuck Bridgham <cbridgha>
Severity:	enhancement
Priority:	P3	CC:	cbridgha, david_williams
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Jim Zhang

2011-08-18 09:26:23 EDT

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

Comment 1 David Williams

2011-09-21 12:33:24 EDT

Is Java EE Tools a better "home" for this request?

Comment 2 Chuck Bridgham

2011-09-21 14:19:47 EDT

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...)

Comment 3 Chuck Bridgham

2011-09-21 14:54:54 EDT

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.