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

Marcel Neuwohner (JIRA) issues at jboss.org
Tue Aug 11 05:12:03 EDT 2015


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

Marcel Neuwohner commented on JBIDE-20071:
------------------------------------------

Is there any way to disable this behavior? We have some really huge jar modules in our war project (10.000+ class files), but no web content in them. As a result, on our developer machines without SSDs Wildfly startup time is at least 3x slower than before this change, also a full publish takes significantly longer.

> 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
>            Assignee: Rob Stryker
>              Labels: new_and_noteworthy
>             Fix For: 4.3.0.Beta2
>
>
> 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)


More information about the jbosstools-issues mailing list