[jbosstools-issues] [JBoss JIRA] (JBIDE-24322) Openshift publisher keeps getting more nested

[Dmitrii Bocharov (JIRA)]

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

Dmitrii Bocharov updated JBIDE-24322:
-------------------------------------
        Steps to Reproduce: 
0) Windows operating system
1) Remove rsync from the PATH. To check if rsync cannot be detected, simply try to run _rsync_ command in the cmd cli. You can do it via multiple ways: a) go to the installation directory of the sygwin -> to the _bin_ directory -> find there _rsync_ binary and rename it. b) if you have cwRsync installed separately, then uninstall it, or also simply remove it. Finally, command _which rsync_ must output _"which: no rsync in  <PATH env var>"_.
2) Create openshift connection in Openshift Explorer
3) create any eap application, e.g. jboss-eap70-openshift
4) wait till pod is built and run.
5) create server adapter
6) make changes in the sources and save them.

Publish will happen. If you continue to do publishes, it will lead to the nested directories.
    Workaround Description:  Make sure to have rsync installed and added to the PATH env variable.
                Workaround: Workaround Exists


added steps to reproduce + workaround

> Openshift publisher keeps getting more nested
> ---------------------------------------------
>
>                 Key: JBIDE-24322
>                 URL: https://issues.jboss.org/browse/JBIDE-24322
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.3.1.Final
>         Environment:  - OS: Windows 7
>  - JbossDev: 10.3.0.0
>  - Openshift Client: 3.4
>  - Openshift Enterprise: 3.4
>  - Workspace location: it's inside a network drive
>            Reporter: Rob Stryker
>            Assignee: Dmitrii Bocharov
>            Priority: Critical
>             Fix For: 4.4.4.Final
>
>
> During a POC, one of the requirements is that developers want to deploy/test their local changes inside a pod before to commit.
> We noticed that during the publishing or local change.
> ​
> The Publish function, always creates a nested deploy directory inside an existing one. 
> For instance inside /opt/eap/standalone/deployments/
> 1st Publish:
>   deploy/server.war/
> 2nd Publish:
>   deploy/deploy/server.war/
> 3nd Publish:
>   deploy/deploy/deploy/server.war/
>  
> So with 3 publish, you end up with 3 deployed same application.
> This happen also inside the local workspaces for the synchronisation:
> .metadata/.plugins/org.jboss.ide.eclipse.as.core/poc-dev at jboss-eap70-openshift
> The EAP7 images is the jboss-eap70-openshift:latest.
>  
> Do you have any idea why this happen?



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