[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10197:
---------------------------------------------
the .settings/ content in your project(s) would be helpful.
The one that works and the one the doesn't and we'll do a diff.
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
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Critical
Labels: jboss
Fix For: 3.3.0.M5, 3.3.0.Beta1
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira