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

Fred Bricon (JIRA) jira-events at lists.jboss.org
Fri Nov 15 09:42:06 EST 2013


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

Fred Bricon commented on JBIDE-13405:
-------------------------------------

We reproduced with a simple(r) setup :
- create java project (dependency)
- create Connector project (connector)
- open connector's deployment assembly page 
- add Project > dependency, change deploy path to lib/dependency.jar
- create a AS7 server w/ Remote Deployment on local machine
- add and publish connector on server
=> dependency.jar deployed as a folder

We had similar issues in the past with deployment of ejb jars in webapps (don't remember exactly), but IIRC the problem was some AbstractFlattenParticipant implementation not recognizing the project as a single root

Assigning back to Rob

                
> 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: server
>    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: Rob Stryker
>             Fix For: 4.1.1.CR1
>
>         Attachments: maven-broken.tar.gz
>
>
> 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


More information about the jbosstools-issues mailing list