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

Martin Malina (JIRA) issues at jboss.org
Thu Jun 11 04:12:04 EDT 2015


     [ https://issues.jboss.org/browse/JBIDE-20037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Malina resolved JBIDE-20037.
-----------------------------------
    Resolution: Done


This is fixed in https://github.com/jbosstools/jbosstools-server/commit/a4805a0f018903e6c6f84962a8784d9b7ccd3ea1 (currently in master).

> 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
>             Fix For: 4.3.0.Beta2
>
>
> 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)


More information about the jbosstools-issues mailing list