[
https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-22578:
-------------------------------------
Sadly I'm not able to replicate this at all, even with this information!
Perhaps this is because I'm using neon and not mars. Once I set the module to have a
path of "../" in the xml file, the eclipse webtools framework stops recognizing
it as a child module and I never get asked to publish it.
[~mmalina] can you verify this isn't replicatable on neon?
Publishing sometimes recursively deletes parent to deploy directory
-------------------------------------------------------------------
Key: JBIDE-22578
URL:
https://issues.jboss.org/browse/JBIDE-22578
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.3.1.Final
Environment: Eclipse Mars.2 Release (4.5.2)
Java 1.8.0_91
Windows 7 64-bit
JBoss EAP 6.4.0
Reporter: Daniel Atallah
Assignee: Rob Stryker
Priority: Blocker
Fix For: 4.4.1.AM1
Attachments: jboss_deployment.jpg, servers.xml
For a number of weeks we've had a number of occurrences where a eclipse workspace
will get corrupted due to the deletion of all files in it.
It seems to have started happening at the time we updated to the 4.3.1 JBoss Tools from
the 4.3.0 JBoss Tools.
We've been able to track the process doing the deleting to the Eclipse process by
using Sysinternals Process Monitor tool
(
https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx).
Our workspaces are structured as follows:
{noformat}
WORKSPACEROOT=$DEVROOT\workspacename
# Custom deploy folder (as specified in the "Deployment" settings for the
configured "Red Hat JBoss Enterprise Application Platform 6.1+") Server
$WORKSPACEROOT\deploy
# Version Control (Mercurial) working directory containing various Eclipse projects that
get published to the Server by the tooling
$WORKSPACEROOT\src
# value specified as a "jboss.server.data.dir" property in the Server launch
configuration VM arguments
$WORKSPACEROOT/server/data
# value specified as a "jboss.server.temp.dir" property in the Server launch
configuration VM arguments
$WORKSPACEROOT/server/tmp
{noformat}
The Server is configured to "Automatically publish when resources change".
What we're seeing is that occasionally when the Server is running and the Mercurial
working copy receives updates, the Incremental Publishing that results from these updates
somehow tries to recursively delete $WORKSPACEROOT.
The eclipse log includes the following:
{noformat}
!ENTRY org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795
!MESSAGE Problems occurred refreshing resources
!SUBENTRY 1 org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795
!MESSAGE Problem finding next change, code: 5
!ENTRY org.jboss.ide.eclipse.as.core 4 1644298244 2016-06-07 16:06:09.207
!MESSAGE Incremental publish failed for module $MODULENAME
!SUBENTRY 1 org.jboss.ide.eclipse.as.wtp.core 4 1644298251 2016-06-07 16:06:09.207
!MESSAGE Could not delete $WORKSPACEROOT. May be locked by another process.
{noformat}
Any idea what might be happening?
Is there some debug logging we can enable to get better visibility to what's going
on?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)