]
Jeff MAURY updated JBIDE-24322:
-------------------------------
Sprint: devex #131 April 2017 (was: devex #131 May 2017 (JBIDE))
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
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@jboss-eap70-openshift
The EAP7 images is the jboss-eap70-openshift:latest.
Do you have any idea why this happen?