|Re: Take existing JS project and make it deployable with WTP [message #1696677 is a reply to message #1696486]
||Wed, 27 May 2015 20:10
| Larry Isaacs
Registered: July 2009
On 5/27/2015 9:19 AM, Alex Dowgailenko wrote:|
> I have a JS project that looks like this:
> I want to now deploy this in Tomcat using WTP but I do not want to move
> these files into separate folders. Currently, it seems I can not include
> specific files in the Deployment Assembly settings page, nor can I
> include the root folder of the project.
> Is there ways to get past this restriction? I am not against introducing
> maven into the project. Thank you.
When working in the domain of a project, as opposed to the workspace, I
don't think "root" is a folder. I think it may be the project, which
isn't the quite same thing as a folder. This may be why the Deployment
Assembly page doesn't offer to include the "root folder".
A long time ago, before the Deployment Assembly page existed, there was
some attempt to allow the root of the project to be used. I also recall
there being a number issues with supporting this. I think the issues
dealt mostly with distinguishing what was meant to be webapp content and
what wasn't. For example, you probably don't want to include any Java
source in that webapp content. Though your current project would not be
affected, such a "feature" would still need to work correctly in more
complex use cases, which proved to be a problem. Thus, it may not be
supported anymore or at least very risky to use even if there was a way
to make it happen.
Is there a problem with using:
which would be the default way that Dynamic Web Projects set up the
"content" folder and should just work?
I'm not sure if maven will help as it typically expects web content in a
sub folder of the project too, i.e. I believe "src/main/webapp" instead
Powered by FUDForum
. Page generated in 0.01606 seconds