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

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

> add embedded to utility deployment assembly (change to deploy-path="/jars/" in org.eclipse.wst.common.component, UI doesn't allow it)

The UI does allow it. You double-click on the deploy-path column and write jars/embedded.jar.  

The resulting published archive looks as follows

{code}
[rob at localhost 1]$ du -a
4	./WebApp1.war/WEB-INF/lib/Utility.jar
8	./WebApp1.war/WEB-INF/lib
4	./WebApp1.war/WEB-INF/classes/pak/TigerSarvlet.class
8	./WebApp1.war/WEB-INF/classes/pak
12	./WebApp1.war/WEB-INF/classes
24	./WebApp1.war/WEB-INF
4	./WebApp1.war/META-INF/MANIFEST.MF
8	./WebApp1.war/META-INF
36	./WebApp1.war
{code}

Exploding Utility jar, we see the following:
{code}
[rob at localhost 1]$ unzip -l  ./WebApp1.war/WEB-INF/lib/Utility.jar
Archive:  ./WebApp1.war/WEB-INF/lib/Utility.jar
  Length      Date    Time    Name
---------  ---------- -----   ----
      612  02-19-2015 02:08   jars/Embedded.jar
       39  02-19-2015 02:05   META-INF/MANIFEST.MF
      261  02-19-2015 02:06   UtilityModel.class
        0  02-19-2015 02:08   META-INF/
        0  02-19-2015 02:08   jars/
---------                     -------
      912                     5 files
{code}

Inside the embedded jar, we see:

{code}
[rob at localhost 1]$ unzip -l jars/Embedded.jar 
Archive:  jars/Embedded.jar
  Length      Date    Time    Name
---------  ---------- -----   ----
       39  02-19-2015 02:05   META-INF/MANIFEST.MF
      264  02-19-2015 02:06   EmbeddedModel.class
        0  02-19-2015 02:08   META-INF/
---------                     -------
      303                     3 files
{code}

So as far as I  can tell, everything works as expected. I believe this use case has been supported for about a year, though I do recall it being a bug in the past. 




> 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.Beta1, 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)