Priority
Normal
Type
Bug 
State
Fixed 
Assignee
Nikolay Chashnikov 
Subsystem
J2EE.Deployment and Run.Generic 
Affected versions
Fixed in
Fixed in build
Next build 
Build
4155
Fixed in build
2
Severity
0
  • Submitted by   Gibson
    3 years ago (03 Mar 2006 12:30)
  • Updated by   root
    3 weeks ago (17 Jan 2010 19:27)
  • Jira: IDEA-31607
    (history, comments)

IDEA-31607

Web module always sets to "Do not package" on startup
0
TestProject.tgz   (288 KB)
I have a JSP module and a Java module - the JSP module depends on the Java module and the Java module exports some named module-level libraries.
In the JSP module I set the named library to "Copy files to ..." and save the config.
The next time that I start up the jsp.iml definition file has been changed and the library is set to "do not package".

To reproduce:
1) unzip the given project
2) copy the jsp.iml file somewhere safe
3) load the project into Idea
4) once the project has finished loading, compare the file jsp.iml with the copy that you made in step 2 - they are different
5) go to the module definition for JSP.iml, the library Logging is set to "do not package" and it should be "copy"

I put this as high because I have never really managed to get a stable JSP module definition since Idea 3.0 - but if this bug is fixed I think I'm finally there ...

Issue was resolved
Comments (4)
 
History (1)
 
Links
  
Gibson
  Gibson
03 Mar 2006 18:00
(3 years ago)
#permalink
Aargh, if I make my project with the changed .iml file it deletes the jar files that I manually put in WEB-INF/lib :((
Gibson
  Gibson
06 Mar 2006 13:27
(3 years ago)
#permalink
And even if I change the Web Module Settings back to "copy files", every time I update my project the setting goes back to "do not package".
Not cool :(
Gibson
  Gibson
07 Mar 2006 20:03
(3 years ago)
#permalink
Yay! Is there a build I can test this in before 5.1.1 gets frozen?
Nikolay Chashnikov
  Nikolay Chashnikov
09 Mar 2006 09:27
(3 years ago)
#permalink
You can try next Demetra EAP build.

BTW, this bug occurs only with a named module-level libraries. As a workaround you can use project-level libraries or unnamed module libraries instead.