History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: IDEABKL-3306
Type: Usability Problem Usability Problem
Status: Open Open
Priority: Normal Normal
Assignee: Nikolay Chashnikov
Reporter: Chris Knight
Votes: 0
Watchers: 1
Available Workflow Actions

Mark as Stalled
Operations

If you were logged in you would be able to see more operations.
IDEA: Backlog

Too restrictive Web Module setup structure

Created: 12 Jul 05 08:45   Updated: 30 Jun 06 19:32
Component/s: J2EE. Deployment and Run, Project Configuration, IDE Configuration, Debugger, Compiling Project
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment: Win XP. Web Module Project (not J2EE or EJB). Local Tomcat Server 5.0 (integrated). Local Oracle DB Server.

Build: 3,397
Severity: Extreme


 Description  « Hide
I've noticed that each build lately has progressively introduced more and more restrictions on how Web Modules must be set-up in IntelliJ. I understand that IntelliJ is adhering to the J2EE Web application structure to aid the ease of deployment. However I feel it is a mistake, that may turn users away, to actually force a certain type of set-up. In previous versions of IntelliJ it is possible to set the 'module root', 'classes dir', 'src dir', 'resources dir' 'exploded dir', and 'deployment dir' to absolutely anything u desired. But now in the latest build this is no longer possible and I must now conform to a specific structure.

For example, IntelliJ 3397 now insists that my 'Web Module exploded dir' must be different from my resources dir's and that my resource dir's must be within my project module root!!Unable to render embedded object: File ((arrgggg) not found.!!). All very annoying, but far worse than that, IntelliJ now insists that my classes dir cannot be in my 'Exploded dir'. This is the most annoying restriction that I've ever seen in an IDE. As a developer I don't want to be restricted in this manner and for very good reasons. This web deployment structure is fine when working with a remote server and wishing to deploy at the same time as building. However its really resource hungry and completely pointless when working with a local server.

Surely when integrated tomcat is being used locally there is no need for the IDE to insist on web deployment. My main problem at the moment is my classes dir is not in my WEB-INF dir because IntelliJ will no longer let me do this. Instead it insists on a separate location. Then when I recompile a file, IntelliJ recompiles the file into my classes dir and then proceeds to copy the file to my deployment WED-INF dir (good god that’s stupid locally!!!). And worse than that it seems to find the need to copy more than just the file I recompiled (sometime copying 100's of unchanged files), really annoying when Hot Swapping ( particularly when it only Hot Swaps the recompiled file...why did it copy all the others???). This is very time consuming and totally unnecessary in a local environment. If my classes dir is in the same location as the web-inf dir then no copying is necessary...just recompile and reload....faster...simpler...the way it used to be!

Also, I should be able to have my 'Web Resources' dir out with my web module content root.

Can someone please look at the possibility of making the restrictions optional.



 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.