[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=13079705#comment-13079705 ] 

Vsevolod Golovanov edited comment on JBIDE-20071 at 6/16/15 9:17 AM:
---------------------------------------------------------------------

JBIDE-19688 suggests that "explodiness" may depend on installed project facets.
Maybe in this task it would be more correct to make Web Fragment Modules deploy exploded, since e.g. Utility Modules probably don't need that.


was (Author: vsevolodgolovanov):
JBIDE-19688 suggests that "explodiness" may depend on installed project facets.
Maybe in this task it would be enough to make Web Fragment Modules deploy exploded.

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