[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-8398) Remote redeployment fails if you switch from exploded to archive

[Rob Stryker (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-8398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-8398.
--------------------------------

    Fix Version/s: 3.3.0.M1
       Resolution: Done


Committed to trunk and branch

> Remote redeployment fails if you switch from exploded to archive
> ----------------------------------------------------------------
>
>                 Key: JBIDE-8398
>                 URL: https://issues.jboss.org/browse/JBIDE-8398
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: deltacloud, JBossAS
>    Affects Versions: 3.2.0.Final
>            Reporter: Andre Dietisheim
>            Assignee: Rob Stryker
>             Fix For: 3.2.1, 3.3.0.M1
>
>         Attachments: change-deployment-mode.png, false-synchronized.png
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> how to reproduce:
> 1) have a AS server adapter for a remote server
> 2) have a WTP project added to it
> 3) make sure the server adapter is set to deploy as exploded war (2nd tab of the server adapter editor "Deploymen": checkbox "Deploy projects as compressed archives" not set (see screenshot1)
> 4) (ev. start the adapter) publish your project
> 5) check the checkbox "Deploy projects as..."
> 6) Choose "Full publish" on your project or "Clean" on the adapter in the servers view
> Result: 
> Deployment fails, the console shows the following exception:
> failed to delete /opt/jboss-as6/server/default/deploy/gwt-helloworld.war
> org.eclipse.rse.services.files.RemoteFileIOException: Operation failed. File system input or output error
> 	at org.eclipse.rse.internal.services.ssh.files.SftpFileService.makeSystemMessageException(SftpFileService.java:449)
> 	at org.eclipse.rse.internal.services.ssh.files.SftpFileService.upload(SftpFileService.java:752)
> 	at org.jboss.ide.eclipse.as.rse.core.archives.RSEZippedJSTPublisher.publishModule(RSEZippedJSTPublisher.java:77)
> 	at org.jboss.ide.eclipse.as.core.publishers.AbstractPublishMethod.publishModule(AbstractPublishMethod.java:77)
> 	at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:67)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1025)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1115)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:948)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:775)
> 	at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2889)
> 	at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:337)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> The adapter stays "[Synchronized]" although the console shows that the deployment failed (see screenshot2).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira