[jbosstools-issues] [JBoss JIRA] (JBIDE-15250) Explode utility jars in EAR/WAR deployments

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-15250:
-------------------------------------

I hand-tested on more servers than wf8.2 to verify it functioned and deployed as expected.  I did have a note to add unit tests later this week, since this is a significant change, though I should have made the JIRA to be more communicative about that intention. 

Our integration tests, on the other hand, are lacking in this regard. We currently have two sets of integration tests:  mgmt, and deployment.   Only the management tests actually start a server, deploy, and check the result. Our deployment "integration" tests are more testing integration with jeetools, WTP, server adapter types, etc, to verify that project creation, deployment assembly, and our server adapters all lead to the expected file structure. 

I will definitely be adding unit tests to verify that the deployment structure is correct for a given hard-coded per-server-type result...  ...  but integration tests involving non-management filesystem deployment against a running server and checking the result is not something we have set up at this time. 

> Explode utility jars in EAR/WAR deployments
> -------------------------------------------
>
>                 Key: JBIDE-15250
>                 URL: https://issues.jboss.org/browse/JBIDE-15250
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: server
>    Affects Versions: 4.0.1.Final
>            Reporter: Kevin Formsma
>            Assignee: Rob Stryker
>             Fix For: 4.3.0.CR1
>
>         Attachments: test-ear.zip
>
>
> For larger projects that utilize utility jars within the EAR, it would be nice to have these deployed exploded as well. This would allow hot code replacement for those utility projects.
> A current work around is to make the utility projects modules so that the tooling treats them as a EJB module and deploys them exploded.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)