Web Module dependency overlay

Hello Matt,

This bug is already reported (http://www.jetbrains.net/jira/secure/IssueNavigator.jspa?mode=hide&requestId=11570).
I'm working on it.

We have a web app which has a dependency on another web app. When
deploying to weblogic app server intellij honors precedence of jsp's
by NOT replacing target files with the same files from the dependency.

However, it appears to overlay the web.xml file from the dependent
project onto the target which is NOT desired -- we want the web.xml
from the target web module and NOT from the dependency web module.

Any way to alter that behavior.

I can't view the issue. It says I don't have permission.

Hello Matt,

I'm sorry. The correct url is http://www.jetbrains.net/jira/browse/IDEADEV-16848.

I can't view the issue. It says I don't have permission.

Will there be a maintenance release that addresses this? Our company has like 40 licenses for version 6.0.5 and this has broken everyone's build process. We are having to do a lot of extra work to get around this and losing productivity.

Please advise when and if a resolution to this problem will be made...

Matt,

The decision process of making a fix in the stable version is always
complex. Rest assured that every issue is carefully evaluated for being
fixed in maintenance release.

Hello Matt,

The mentioned bug relates to Selena EAP builds. It shouldn't occur in IDEA
6.0.5. Could you please attach your .iml files?

Will there be a maintenance release that addresses this? Our company
has like 40 licenses for version 6.0.5 and this has broken everyone's
build process. We are having to do a lot of extra work to get around
this and losing productivity.

Please advise when and if a resolution to this problem will be made...

This is two web modules of a larger ear module. broker has common as a dependency; broker is NOT deployed.

The problem occurs when you change and rebuild common THEN change and/or rebuild broker, the common module web.xml overwrites the broker web.xml. Simply rebuilding broker without changes to common does NOT result in the overwrite.

Would love a simple configuration change if it fixed this problem -- even manually editing the iml files would be ok since we store them in source control and everyone shares.

^ ^ ^

Meant to say above common is NOT deployed. broker is deployed

Hello Matt,

Are "broker" and "common" both included in EAR module? Or only "broker" is?

This is two web modules of a larger ear module. broker has common as
a dependency; broker is NOT deployed.

The problem occurs when you change and rebuild common THEN change
and/or rebuild broker, the common module web.xml overwrites the broker
web.xml. Simply rebuilding broker without changes to common does NOT
result in the overwrite.

Would love a simple configuration change if it fixed this problem --
even manually editing the iml files would be ok since we store them in
source control and everyone shares.

broker and common are included in the ear module along with three more web apps and 2 ejb projects

Hello Matt,

Try to exclude "common" from EAR module. There is no need to include "common"
in EAR because it is included in "broker" which is included in EAR.

broker and common are included in the ear module along with three more
web apps and 2 ejb projects

Sorry for the confusion Nikolay. Common is excluded from the ear build. The problem occurs specifically in the war files when we build them. Changes to common with a rebuild do not cause the file to be overlayed in the broker application but a rebuild of the broker application AFTER a change has been made in the common application results in the common web.xml file overwriting the file in broker which has a dependency on common.

Hello Matt,

I've reproduce the bug at last. It is already fixed in Selena EAP build 7020
but I'm afraid the fix cannot be backported to 6.0.x branch.

BTW why do you need to change common web.xml which isn't deployed?

Sorry for the confusion Nikolay. Common is excluded from the ear
build. The problem occurs specifically in the war files when we build
them. Changes to common with a rebuild do not cause the file to be
overlayed in the broker application but a rebuild of the broker
application AFTER a change has been made in the common application
results in the common web.xml file overwriting the file in broker
which has a dependency on common.

You don't have to change the web.xml file and in fact we don't since, like you said, it isn't deployed. It happens regardless of what file in common you change.

Hello Matt,

The bug reproduces only if you invoke "Compile" action on "broker" module.
If you click "Make module broker" or "Make project" the bug won't occur.
So you should use these "Make" actions.

You don't have to change the web.xml file and in fact we don't since,
like you said, it isn't deployed. It happens regardless of what file
in common you change.