[
https://issues.jboss.org/browse/JBIDE-21835?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-21835:
-------------------------------------
[~mlabuda] I am not able to replicate. When I create a new os3 server adapter, the web
project is automatically added as a module under the server. Furthermore, a breakpoint
set on OpenShiftPublishController.publishStart(etc) never gets hit when server is in
'stopped' state.
When the server is started, a breakpoint on OpenShiftPublishController.publishFinish(etc)
also shows a deploy-directory of
/home/rob/apps/eclipse/workspaces/runtime-EclipseApplication/.metadata/.plugins/org.jboss.ide.eclipse.as.core/p8@eap-app/deploy
If I check the deploy folder inside publishFinish but before the final rsync is executed,
we see no change to the deployment markers. There's no .dodeploy marker created before
the rsync.
I'm not able to replicate your issue at all. [~fbricon]?
Server adapter: incremental deployment is broken
------------------------------------------------
Key: JBIDE-21835
URL:
https://issues.jboss.org/browse/JBIDE-21835
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Fred Bricon
Assignee: Rob Stryker
Priority: Blocker
Fix For: 4.3.1.CR1
Running OS 3.1.1 from
https://github.com/redhat-developer-tooling/openshift-vagrant/tree/master...
Deploy an eap basic app on openshift,
import the kitchensink code in the workspace
wait for the application to deploy and run on openshift
Issue #1
- when creating a server adapter from the OpenShift Explorer menu "Server
Adapter...", on the eap service, the server has no module. The project is treated as
a magic project.
- After making a change to the index page and saving, the page is incrementally pushed to
the openshift server, and then the ROOT.war restart. It's not supposed to
Issue #2
- create a new server adapter from the Servers view. Add the kitchensink project as a
module to the last page of the wizard
- jbosstools-kitchensink.war is deployed to the remote server. Both ROOT.war and
jbosstools-kitchensink.war start, access to the / context root fails. It's been
superseded by jbosstools-kitchensink
- local change is not pushed immediately to the server. module restart happens before the
change is effective.
(Fred indicates this issue was not replicatable on most recent test)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)