[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6024) JBoss AS adapter deploys only recently changed files and removes everithing else

[ https://jira.jboss.org/jira/browse/JBIDE-6024?page=com.atlassian.jira.plu... ] Denis Golovin commented on JBIDE-6024: -------------------------------------- When project deployed to the server there are two parameters to consider: 1. What kind of deployment it is (see org.eclipse.wst.server.core.IServer) PUBLISH_AUTO - publish kind constant (value 3) indicating an automatic publish request. PUBLISH_CLEAN - publish kind constant (value 4) indicating a publish clean request PUBLISH_FULL - publish kind constant (value 2) indicating a full publish request. PUBLISH_INCREMENTAL - publish kind constant (value 1) indicating an incremental publish request. 2. What status is for deployed module (see org.eclipse.wst.server.core.IServer) PUBLISH_STATE_FULL - publish state constant (value 3) indicating that a full publish is required. PUBLISH_STATE_INCREMENTAL - publish state constant (value 2) indicating that an incremental publish is required PUBLISH_STATE_NONE - publish state constant (value 1) indicating that there is no publish required. PUBLISH_STATE_UNKNOWN - Publish state constant (value 0) indicating that it's in an unknown state Right after start all modules are in PUBLISH_STATE_UNKNOWN until first publish is happened. then after publishing module publish state gets updated usually to PUBLISH_STATE_INCREMENTAL. What is happened now right after start first publish happens and it is FULL_PUBLISH kind. It starts from EAR module and it has publishing state PUBLISH_STATE_UNKNOWN which gets converted to PUBLISH_STATE_FULL because if state is unknown full publish required. Publisher nuke all content of ear deployment folder and started to publish each child module. All of them have PUBLISH_STATE_UNKNOWN and they get deployed properly until it gets to WAR module which for unknown reason have PUBLISH_STATE_INCREMENTAL. This state means to publish only resources reported in publish delta. This leads to problem because ear publishing was started form "nuke everything" and that's why only last changed files are deployed for WAR module. I'm not sure if the same can happen for EJB module. IMO problem is in JstPublisher which just delete deploy target folder content without considering that other modules can be published as sub folders and . For EAR publishing it should delete everything except folders that are targets for other modules. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira