[jbosstools-issues] [JBoss JIRA] (JBIDE-19043) Error publishing jar inside utility project inside ear project

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-19043:
-------------------------------------

Basically, wtp is somehow treating the jar inside the utility project as yet another child module. This means it gets its own publish call. Due to some bad logic in my code, we were actually attempting this publish when we should have been ignoring it. Why should we be ignoring it? Because the utility project was already zipped, which means the installer jar is already in the zipped util output jar, and further requests can be ignored. 

Basically, when we zip the util, it already has the installer... so when we get a request to publish the installer (or any other "child" of the utility project) directly after that, we should ignore it. 

> Error publishing jar inside utility project inside ear project
> --------------------------------------------------------------
>
>                 Key: JBIDE-19043
>                 URL: https://issues.jboss.org/browse/JBIDE-19043
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.2.Final
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.2.3.Final, 4.3.0.Beta1
>
>
> While verifying JBIDE-18862 I wanted to have some really big file to deploy so that I could see is an existing *.dodeploy marker is removed before the copying begins.
> So I created an ear project with a nested dynamic web project and utility project. Inside this utility project's src dir I copied JBDS installer jar. Then I tried to deploy the ear to a WildFly 8.2 server (both stopped and running).
> It seemed to work, the utility jar had 574 MB. But the tooling showed me this error:
> Publishing to wildfly has encountered a problem:
> {code}
> Error renaming /Volumes/Data/jbossqa/wildfly-8.2.0.Final/standalone/tmp/tmp582268190747176162.jar to /Volumes/Data/jbossqa/wildfly-8.2.0.Final/standalone/deployments/earproj.ear/lib/utilproj.jar/jboss-devstudio-8.0.2.GA-v20150114-2029-B382-installer-standalone.jar. 
> This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.
> You may adjust these settings in the server editor.
> {code}
> It's true that this was on a different FS, but both the tmp and deploy dirs were one FS, so that should be fine.
> And just to be sure, I tried the same on the same FS and the error was the same:
> {code}
> Error renaming /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/tmp/tmp7876542570838575938.jar to /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/deployments/earproj.ear/lib/utilproj.jar/jboss-devstudio-8.0.2.GA-v20150114-2029-B382-installer-standalone.jar. 
> This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.
> You may adjust these settings in the server editor.
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)