[
https://issues.jboss.org/browse/JBIDE-20037?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-20037.
---------------------------------
This works now, but I noticed a weird thing.
After playing with this a bit in a few dynamic web projects, the reaction of the list of
jars shown in Project Explorer started to be slower or it would not refresh at all.
For example when I removed the org.jboss.metadata module from
jboss-deployment-structure.xml and saved, it would take maybe 5 seconds for the jars to
disappear (normally it was instant). When I added the module back and saved, it would not
show up at all unless I either refreshed the view or right-clicked the project, went to
Properties and checked the Java Build Path there - the newly added jars would be visible
there. And after closing the properties window, the list in Project Explorer view would
now show the new jars as well.
I almost created a JIRA for this, but then I restarted JBDS and now the refresh is
immediate again, so I'm not sure what caused it.
Verified in JBDS 9.0.0.Beta1 B50.
jboss-deployment-structure.xml is not used if added to an existing
project
--------------------------------------------------------------------------
Key: JBIDE-20037
URL:
https://issues.jboss.org/browse/JBIDE-20037
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.3.0.Beta1
Reporter: Martin Malina
Assignee: Rob Stryker
Labels: respin-a
Fix For: 4.3.0.Beta1
This is a corner case of JBIDE-18377 which was fixed in 4.3.0.Beta1.
When you import a project with an existing jboss-deployment-structure.xml, the modules
that are defined in that file are now added as jars to the build path of the project
(thanks to JBIDE-18377). But, as discovered by Rob, if you only add the file after the
project was created, it will not be picked up ("due to aggressive caching and a
missing listener").
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)