[jbosstools-issues] [JBoss JIRA] (JBIDE-22578) Publishing sometimes recursively deletes parent to deploy directory

[Martin Malina (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13265597#comment-13265597 ] 

Martin Malina commented on JBIDE-22578:
---------------------------------------

I tried this, but I cannot reproduce.
[~datallah], perhaps you could provide a simplified project that can reproduce this? Or some steps? Here's what I tried to do in Mars with JBoss Tools 4.3.1 installed:
1. Set up an EAP 6.4 server
2. Set up the server to use $WORKSPACE/deploy for deployment and $WORKSPACE/server/tmp for tmp dir
3. Create a dynamic web project
4. Create a java project
5. Set up Deployment Assembly on the dynamic web project to include the java project
Now I started the server and deployed and all was fine. But this didn't have ../ in the deploy path. The .settings file contained this:
{code}
<dependent-module archiveName="javaproj.jar" deploy-path="/WEB-INF/lib" handle="module:/resource/javaproj/javaproj">
            <dependency-type>uses</dependency-type>
        </dependent-module>
{code}
So I changed it to deploy-path="../"
I restarted Eclipse, just to be sure it picks up my changes. Now the project properties showed the deploy-path for my sub-module as ../javaproj.jar. When I wanted to deploy the dynamic project, this time the java project no longer appeared to be part of this. And when I did deploy it, indeed the jar was nowhere to be found on the filesystem. Then I added a jsp file to the dynamic project which cause a republish. But nothing got deleted incorrectly.

> 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: Martin Malina
>            Priority: Blocker
>             Fix For: 4.4.1.AM2
>
>         Attachments: jboss_deployment.jpg, jboss_tools.20160630.stdout.log, 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)