[
https://issues.jboss.org/browse/JBIDE-16907?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-16907.
---------------------------------
Resolution: Done
I'm going to say for now that this behavior is expected, definitely.
What's actually happening here is that no publish event has taken place. Why not?
Well, a server in management mode takes no action on a publish request to a stopped
server. In fact, we pretend the publish request never happened. It would be wrong of us to
mark something as synchronized if it's not.
This is replicatable if you have a web project that SHOULD be deployed on server start,
but isn't. Maybe you use the 'add / remove to a server' action to add a web
project to such a server, and then you start the server.
Since our servers attempt to publish BEFORE startup, and our management-style servers
ignore that request, a manual publish request is required once the server has started.
For now that's just the way it is.
We may consider caching that request somewhere and initiating a publish request *after*
the server is started, but that would be an issue for a maintenance release.
For now this is expected behavior.
Server publish state not shown for local server with management
operations
--------------------------------------------------------------------------
Key: JBIDE-16907
URL:
https://issues.jboss.org/browse/JBIDE-16907
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Beta1
Reporter: Lucia Jelinkova
Assignee: Rob Stryker
Fix For: 4.2.0.Beta2
Attachments: local-mng.jpg, local.jpg
When I create a local server and start it, both server state and server publish state are
displayed on server's view.
!local.jpg!
However, when I do the same with local server that prefers management operations, only
server state is shown.
!local-mng.jpg!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)