[
https://issues.jboss.org/browse/JBIDE-13405?page=com.atlassian.jira.plugi...
]
Chris Roberts commented on JBIDE-13405:
---------------------------------------
Done. I haven't been able to fully test this on a broken eclipse but looking at the
source yesterday I'm 99.9% certain it will recreate the issue and I just don't
have time right now to go back and break my eclipse again to prove it, I already lost
quite a bit of time on this one... Hope you understand.
If it doesn't error on publish for you then let me know.
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
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