[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-10197:
--------------------------------
Fix Version/s: LATER
(was: 3.3.x)
The only thing I can think of after plenty of time testing is that this is related to
JBIDE-7472, which is a much earlier bug that's been around for a long long time,
upstream in WTP. It seems their classpath container actually scans the contents of
webinf/lib, and adding or removing files to it has always been... ... ... dangerous.
Putting files directly in the folder has never worked as we wanted it to, from the
beginning.
Most of the biggest bugs were cleared out, but there were always ones like this left,
which were difficult and inconsistant to replicate. JBIDE-7472 relates to removal of files
from web-inf/lib, and this one seems to relate to adding files there directly.
I wish there was more that could be done, but at this point, I'm stumped.
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL:
https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers, UpStream
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Labels: jboss
Fix For: LATER
Attachments: org.eclipse.wst.common.components,
org.eclipse.wst.common.components
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira