[jbosstools-issues] [JBoss JIRA] (JBIDE-17267) Broken module factories (upstream) can break astools module deployment

[Rob Stryker (JIRA)]

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

Rob Stryker resolved JBIDE-17267.
---------------------------------

         Assignee: Rob Stryker
    Fix Version/s: 4.2.0.Beta2
       Resolution: Done


Fixed here: https://github.com/jbosstools/jbosstools-server/commit/2c00b45888a4028b3fa12d660d5a9a3ac0949f19

> Broken module factories (upstream) can break astools module deployment
> ----------------------------------------------------------------------
>
>                 Key: JBIDE-17267
>                 URL: https://issues.jboss.org/browse/JBIDE-17267
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.Beta2
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 4.2.0.Beta2
>
>
> If a call to a module's "getChild()" method throws an unexpected exception, our publish utility projects are not prepared to handle it. 
> 1) Install eclipse libra
> 2) modify ASTools as.core/plugin.xml
>     a) Add           <moduleType types="osgi.bundle" versions="1.0"/>   under each jboss runtime type to add support for libra osgi modules
> 3) Create a faceted project, add osgi.bundle facet
> 4) Create dynamic web project
> 5) Create wildfly server
> 6) right-click wildfly server, add / remove modules. 
> 7) Expect to see two module types in the view
> Step 7 fails. The view is empty. No modules in the workspace are deployable. 



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)