[jbosstools-issues] [JBoss JIRA] (JBIDE-26305) Jars inside an EAR application are not compressed

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-26305:
---------------------------------------

Thanks, [~rob.stryker], for the detailed explanation. Note that I was merely trying to present what the customer was struggling with. And at the first sight it seemed wrong that a jar would ever be exploded, my intuition said it was wrong. If it indeed was wrong, then the default should be always zipped for jars. But since you say that WildFly should support deployment of exploded jars with no problem, then I agree with you that if the deployment indeed breaks for exploded jar and works with zipped jar for the customer, then that seems like a problem with the app server and not devstudio. 

[~rick_wagner], can you relay Rob's explanation to the customer and let us know if there's anything we can do? Right now it seems like it could be a problem with EAP itself.

> Jars inside an EAR application are not compressed
> -------------------------------------------------
>
>                 Key: JBIDE-26305
>                 URL: https://issues.jboss.org/browse/JBIDE-26305
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>
> A customer has reported an issue where an ear project, when deployed to EAP 7.1, contains exploded jars which then breaks his app. It seems that in his case it happens both in the case of a jar inside a war inside an ear, as well as just a jar inside an ear.
> Also, when the customer deploys the same app in the same workspace and same eclipse to EAP 6.4, it works fine - all the jars are zipped.
> The customer reports that he can change this behavior in the Deployments tab of the server editor, but it would be nice to be able to define this beforehand in a config file.
> I tried to reproduce this in devstudio 12 and in my case the behavior was the same with both EAP 6.4 and 7.1 - in both cases an included jar was exploded which I think is wrong.
> So two main things to consider:
> 1. Is this a bug? I believe it is - a jar lib should always be zipped by default. Or do you disagree?
> 2. Is there a way to specify if a module of an EAP is zipped or not in a config file? If not, can this be added?



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)