[jbosstools-issues] [JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-22773:
-------------------------------------

The first portion of the error seems very strange to me. We typically use renameTo, which only usually fails when moving from one filesystem to another. However, here, the two paths are definitely starting with the same prefix, and the renameTo should work without error. 

C:\work\runtime-JBossTools\.metadata\.plugins\org.eclipse.wst.server.core\tmp1018478665720865429.MF to C:\work\runtime-JBossTools\.metadata\.plugins\org.jboss.ide.eclipse.as.core\test1 at eap-app\deploy\ROOT.war\META-INF\MANIFEST.MF


Both paths start with C:\work\runtime-JBossTools\.metadata\.plugins\  so there's no real reason for the renameTo to fail. 

And why the rsync fails is even more confusing. Is that because it's using cyg paths? or is that appropriate? 

> Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-22773
>                 URL: https://issues.jboss.org/browse/JBIDE-22773
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift, upstream
>    Affects Versions: 4.4.1.AM2
>            Reporter: Jeff MAURY
>            Assignee: Jeff MAURY
>              Labels: server
>             Fix For: 4.4.2.AM3
>
>         Attachments: screenshot-1.png
>
>
> When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error:
> [^screenshot-1.png]



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)