[jbosstools-issues] [JBoss JIRA] (JBIDE-20037) jboss-deployment-structure.xml is not used if added to an existing project

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-20037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079973#comment-13079973 ] 

Rob Stryker commented on JBIDE-20037:
-------------------------------------

I've noticed similar things, but I've been unable to track down what could possibly be causing it. My debugging usually indicates that my code is run, and run properly, and so the bug could be somewhere in jdt / classpath management, where it delays or buffers changes in case of multiple changes.  

I really have no evidence of this though,  just an idea I thought sounded possible ;) 

> 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)