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

[Rob Stryker (JIRA)]

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

Rob Stryker reassigned JBIDE-24322:
-----------------------------------

    Assignee: Rob Stryker


> 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
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>
> Hi Max,
> Dominik Wotruba gave me your contact and I am writing you this email with the hope that you can give us an hint about the following situation with the Openshift Server adapter plugin.
> 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)