[jbosstools-issues] [JBoss JIRA] (JBIDE-13405) Deploying a RAR with JAR inside fails using remote systems via SSH

[Chris Roberts (JIRA)]

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

Chris Roberts commented on JBIDE-13405:
---------------------------------------

I did a bunch more research on this last night. It seems org.jboss.ide.eclipse.as.core/AbstractServerToolsPublisher.java expects the RSE handlers to be able to identify and package jars, related to the forceZip code. 

This seems to work for local (it seems the RSE local handler deals with the archive, possibly with copyFromArchive), but the RSE SSH/FTP/dstore connectors don't seem to be prepared to deal with forceZip. So JBoss makes the directory expecting the handler to uncompress the jar into it, and for SSH/FTP/dstore this doesn't work. I tried to modify the SFTP connector to deal with the JBoss forceZipped archives, but I couldn't get something in the time I had.

I was able to make a workaround for myself for disabling forceZip (forceZip = false) in org.jboss.ide.eclipse.as.core/AbstractServerToolsPublisher.java. This obviously means for remote systems the upload takes a long time with a lot of class files & I'm relying on a patched org.jboss.ide.eclipse.as.core, but I've got something working for now.
                
> Deploying a RAR with JAR inside fails using remote systems via SSH
> ------------------------------------------------------------------
>
>                 Key: JBIDE-13405
>                 URL: https://issues.jboss.org/browse/JBIDE-13405
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 4.0.0.Final
>         Environment: JBoss AS 7.1.1 Final, Eclipse Juno SR1, JBoss Tools 4.0.0 Final
>            Reporter: Chris Roberts
>            Assignee: Fred Bricon
>
> Exploding dependant jars seems to have issues for rars. I didn't work out if this is a problem in JBoss Tools or RSE. I suspect a little of both. It seems looking at the source that only the 'Local' RSE adapter correctly explodes deployments?
> 1) Create a maven project, set the packaging to rar
> 2) Create a second maven project, set the packaging to jar
> 3) Include the jar as a maven compile dependency of the rar
> 4) Import both into eclipse
> 5) Deploy to a remote (JBoss AS) server via RSE SSH/dstore/FTP fails
> It seems the JBoss Server Adapter (I think) creates the directory:
> xxxxx-1.0.rar/xxxxx-1.0.jar/
> on deployment. It then requests upload for the jar over the top of the directory which fails. With FTP this looks like:
> CD xxxxx-1.0.rar/
> MKD xxxxx-1.0.jar
> STOR xxxxx-1.0.jar <fails because directory exists>
> This is my first bug opened on JBoss/eclipse, so please point me on if you think this should be opened on RSE, but I think looking at the source it belongs here.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira