[jbosstools-issues] [JBoss JIRA] (JBIDE-20071) Allow deploying exploded jars to war/WEB-INF/lib

[Vsevolod Golovanov (JIRA)]

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

Vsevolod Golovanov commented on JBIDE-20071:
--------------------------------------------

I've linked a pull request.
It makes Webfragments and EJBs in WARs deploy exploded. EJBs in WARs too, because the preference should be to deploy everything exploded, and there is no reason anymore to make such an exception.
I've verified that the change works, and that there are no test failures.

The ones that still deploy packaged are Utility JARs (there is the JBIDE-15250 devoted to them) and Application Clients (not sure if something needs to be done about them).

> Allow deploying exploded jars to war/WEB-INF/lib
> ------------------------------------------------
>
>                 Key: JBIDE-20071
>                 URL: https://issues.jboss.org/browse/JBIDE-20071
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: server
>    Affects Versions: 4.2.3.Final
>         Environment: JBoss Developer Studio 8.1.0.GA
>            Reporter: Vsevolod Golovanov
>
> There were JBIDE-10318, JBIDE-9836 before. They were pretty strict in that deploying expoded JARs in WAR/WEB-INF/lib is not allowed for some reason. The only actual reason seemed to be that the server at the time refused to deploy such structure. Maybe the server was in the wrong? This was fixed in AS7-4704.
> Now with Wildfly 8.2.0.Final exploded JARs in WAR/WEB-INF/lib deploy correctly, at least Weld, EJB, JSF seem to work fine.
> The main use case for this is creating a modular web application, with different parts implemented in separate projects. Hot deploying of resources, such as Facelets' XHTMLs, is crucial for development. So the JARs need to be exploded.



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