[JBoss JIRA] (JBDS-3609) update splashscreen, about gfx, start icon for developers.redhat.com
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3609?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-3609:
--------------------------------
Resolution: (was: Done)
Assignee: James Cobb (was: Nick Boldt)
Despite this being done a month ago, we've just been told by [~james.cobb] that we have to reskin the website because RHD logo is verboten. Reopening and assigning to [~james.cobb] so he can provide replacement graphics on this JIRA.
> update splashscreen, about gfx, start icon for developers.redhat.com
> --------------------------------------------------------------------
>
> Key: JBDS-3609
> URL: https://issues.jboss.org/browse/JBDS-3609
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build, installer, p2-product
> Reporter: Max Rydahl Andersen
> Assignee: James Cobb
> Priority: Blocker
> Fix For: 10.0.0.Alpha1
>
> Attachments: about-jbds10.png, launcher-icons-jbds10.png, splash-jbds10.png
>
>
> update splashscreen, about gfx, start icon for developers.redhat.com
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22578) Publishing sometimes recursively deletes parent to deploy directory
by Daniel Atallah (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi... ]
Daniel Atallah updated JBIDE-22578:
-----------------------------------
Summary: Publishing sometimes recursively deletes parent to deploy directory (was: Publishing recursively sometimes deletes parent to deploy directory)
> 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
>
> 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)
9 years, 10 months
[JBoss JIRA] (JBIDE-22578) Publishing recursively sometimes deletes parent to deploy directory
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22578:
--------------------------------------
Assignee: Rob Stryker
> Publishing recursively sometimes 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
>
> 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)
9 years, 10 months
[JBoss JIRA] (JBIDE-22578) Publishing recursively sometimes deletes parent to deploy directory
by Daniel Atallah (JIRA)
Daniel Atallah created JBIDE-22578:
--------------------------------------
Summary: Publishing recursively sometimes 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
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)
9 years, 10 months