More web app issues
Not sure where exactly to put this, because in some ways the existing web app approach technically works I guess this may fall into a feature request.
The problem is that I want to point my project at an existing source controlled web app. My company decided against the IntelliJ standard of having a resources directory that gets copied to the ROOT of the web app upon deployment/compile.
Here is what would be useful; in the Web Resource Directories section the dialog for each entry should have:
path
relative path
list of excluded directories
checkbox for recursive (true/false)
This would allow two standard entries that mimmick normal webapp deployments and it would allow me the flexibility to use IntelliJ and abide by my companies various directory policies.
path: {path/to/webapp/WEB-INF}
relativePath: /WEB-INF
excluded-directories: none
recursive: true
path: {path/to/webapp/}
relativePath: /
excluded-directories: WEB-INF (and optionally META-INF)
recursive: true
Please sign in to leave a comment.
I have opened a request to have this feature implemented, you can see it here:
http://www.jetbrains.net/jira/browse/FBQF-567
Please vote on it.
I may not be completely understanding the issue, but it seems like you can
do what you're asking, there is no reason why you can't exclude
directories, even WEB-INF (though that's kind of weird). You can probably
accomplish what you want by making multiple web app modules.
R
Robert S. Sfeir wrote:
Yes, as a work-around you can do it with multiple web app modules, but implementing this
request would make it much more straight forward. When you are working on a single web
application, you really don't want to have to set up multiple web application modules just
to get around a couple of missing options on the web resource directories.
To make it really useful, I would like to see a couple of tree views in the web resources
configuration panel, similar to the Paths tab. The left tree should display all of the
folders that are included in the content based on the paths tab. The right one should show
a "deployment view" of the web resources directories. The user should be able to select a
folder in the left tree and drag it over to the right tree placing it in the hierarchy where
it needs to be. There should also be options to add new (sub)folders to the deployment view
tree as well as including/excluding the content sub-folders in the deployment view tree.
Tim
Gabriel Harrison wrote:
I don't understand... if you have WEB-INF/ under path/to/webapp/,
wouldn't it be enough to just have the one entry for path/to/webapp/ ?
/Kreiger
Attachment(s):
signature.asc