[jbosstools-issues] [JBoss JIRA] (JBIDE-13730) Server adapter state [Republish] although Repository is uptodate
Rob Stryker (JIRA)
jira-events at lists.jboss.org
Mon Nov 25 04:03:09 EST 2013
[ https://issues.jboss.org/browse/JBIDE-13730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926417#comment-12926417 ]
Rob Stryker commented on JBIDE-13730:
-------------------------------------
Re-posting here from the duplicate issue:
state constnats are available in IServer.STATE_XXX or IServer.PUBLISH_STATE_XXX. Both servers and modules may have states (started / stopped / unknown ) or publish states (requires a full, incremental, unknown, or none publish). After a successful publish, you'd mark as NONE.
setModuleState(module[], int state); sets the state next to the module (started / stopped, may also be IServer.STATE_UNKNOWN)
setModulePublishState(module, IServer.PUBLISH_STATE_FULL or PUBLISH_STATE_INCREMENTAL or PUBLISH_STATE_NONE); (full indicates we still need a full publish, incremental means we require an incremental publish, none indicates the publish is now fully synchronized)
setServerPublishState(int) - indicates whether the server itself requires a full / incremental / or no publish
setServerState(int) - indicates whether the server is started / stopped / unknown / etc
> Server adapter state [Republish] although Repository is uptodate
> ----------------------------------------------------------------
>
> Key: JBIDE-13730
> URL: https://issues.jboss.org/browse/JBIDE-13730
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.1.0.Alpha1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Fix For: 4.2.x
>
> Attachments: republishsync.png
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list