July 2016 - jbosstools-issues - Jboss List Archives

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-22578: ----------------------------------- Assignee: Martin Malina (was: Rob Stryker) > 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.AM1 > > 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)

9 years, 9 months

1
0
0 / 0

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22578: ------------------------------------- [~mmalina] can you help get a test project that can recreate this issue? > 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.AM1 > > 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)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-726) Need additional/new docs for the Docker and Openshift "explorer" features targeting the local CDK

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-726?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-726: ------------------------------------ Hi [~ldimaggio], from the email, I see that the requested information was this: I see the following use cases: 1. Installing CDK on Win/Mac/Linux manually without our all-in-one installer. As far as I understand it will be covered by the CDK get started guide. 2. Using manually installed CDK in JBDS. Users have to do a few additional but not obvious steps in JBDS to set up a CDK (create a CDK server adapter, set up oc cli tool, etc). 3. Using our all-in-one windows installer. Some info about how to use the installer. 4. Getting started with CDK in JBDS after using our all-in-one win installer. In that case the installer does set up a CDK in JBDS for you and you don't need to do steps from #2. So, this case is the next step for #2 and #3. I think we've covered all of this in the CDK tooling article here: https://access.redhat.com/articles/2388671 What do you think, Len? I think we can probably close this issue. > Need additional/new docs for the Docker and Openshift "explorer" features targeting the local CDK > ------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-726 > URL: https://issues.jboss.org/browse/TOOLSDOC-726 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: General documentation issues > Affects Versions: 9.1 GA > Reporter: Len DiMaggio > Assignee: Misha Ali > Fix For: 9.1 GA > > > Following up on an email thread related to: > We should cover both the Docker and Openshift "explorer" features targeting the local CDK. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-121) [content assist] Content Assist templates still contain traces of Java [EBZ#489320]

by Angel Misevski (JIRA)

[ https://issues.jboss.org/browse/ERT-121?page=com.atlassian.jira.plugin.sy... ] Angel Misevski reassigned ERT-121: ---------------------------------- Assignee: Angel Misevski > [content assist] Content Assist templates still contain traces of Java [EBZ#489320] > ----------------------------------------------------------------------------------- > > Key: ERT-121 > URL: https://issues.jboss.org/browse/ERT-121 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Angel Misevski > Labels: General, bzira > > Each content assist template should be reviewed such that it is applicable to JavaScript developers. > For instance, here's an excerpt from the live JSDT catchblock template: > ${exception_var}.printStackTrace() -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-154) Allow for specifying labels when running a container [EBZ#485913]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-154?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston resolved ERT-154. ------------------------------- Fix Version/s: Neon.1 (4.6) (was: Neon (4.6)) Resolution: Done > Allow for specifying labels when running a container [EBZ#485913] > ----------------------------------------------------------------- > > Key: ERT-154 > URL: https://issues.jboss.org/browse/ERT-154 > Project: Eclipse Release Train > Issue Type: Enhancement > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: Docker, bzira > Fix For: Neon.1 (4.6) > > > Labels can be specified on the container when it is created. The wizard/launcher could also provide this feature in the UI. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3879) AERI - Closing the 'configure projects' dialog disables enabled projects

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3879?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3879: ---------------------------------- In the Alpha1 target platform: org.eclipse.epp.logging.aeri.core_1.100.0.v20160330-0740.jar 19-May-2016 19:02 165K org.eclipse.epp.logging.aeri.ide_1.100.0.v20160330-0740.jar 19-May-2016 18:49 365K In the Final target platform: org.eclipse.epp.logging.aeri.core_2.0.1.v20160602-0457.jar 13-Jun-2016 19:18 165K org.eclipse.epp.logging.aeri.ide_2.0.1.v20160605-1811.jar 13-Jun-2016 19:17 367K So, yeah, this was fixed upstream in AERI some time ago. See JBIDE-22418. If you want to try to reproduce this problem with 10.0.0.Final instead of Alpha1, feel free. Or close it because this was already fixed upstream. :D cc: [~marcel.bruch] > AERI - Closing the 'configure projects' dialog disables enabled projects > ------------------------------------------------------------------------ > > Key: JBDS-3879 > URL: https://issues.jboss.org/browse/JBDS-3879 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: aeri, target-platform > Affects Versions: 10.0.0.Alpha1 > Environment: Version: 10.0.0.Alpha1 > Build id: Alpha1-v20160430-1625-B5264 > Build date: 20160430-1625 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 10.0.1.AM1 > > Attachments: after.png, before.png > > > To recreate: > * Navigate to: Preferences->General->Error Reporting > * Open 'configure projects' dialog > * Enable one or more projects, click on "Enable" > * Open 'configure projects' dialog > * Close the dialog (select the 'x' at upper right) > * Open 'configure projects' dialog > * Observe that the selections are now disabled -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3879) AERI - Closing the 'configure projects' dialog disables enabled projects

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3879?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-3879: -------------------------------- Assignee: Len DiMaggio (was: Nick Boldt) > AERI - Closing the 'configure projects' dialog disables enabled projects > ------------------------------------------------------------------------ > > Key: JBDS-3879 > URL: https://issues.jboss.org/browse/JBDS-3879 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: aeri, target-platform > Affects Versions: 10.0.0.Alpha1 > Environment: Version: 10.0.0.Alpha1 > Build id: Alpha1-v20160430-1625-B5264 > Build date: 20160430-1625 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 10.0.1.AM1 > > Attachments: after.png, before.png > > > To recreate: > * Navigate to: Preferences->General->Error Reporting > * Open 'configure projects' dialog > * Enable one or more projects, click on "Enable" > * Open 'configure projects' dialog > * Close the dialog (select the 'x' at upper right) > * Open 'configure projects' dialog > * Observe that the selections are now disabled -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13671: ------------------------------------ Per suggestion/agreement from Max & Mickael, I've also merged this PR: https://github.com/jbosstools/jbosstools-build/pull/225 > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.1.AM1 > > Attachments: after-jgit.png, after-jgit2.png, arq-dirty-workspace-compare1.png, arq-dirty-workspace-compare2.png, arq-dirty-workspace-compare3-bigger-change.png, arq-dirty-workspace-compare4-bigger-change.png, base-before-after-jgit.png, before-jgit.png, before-jgit2.png, jbide13671-before-and-after.png, server-before-after-jgit-3-different-timestamps.png, server-before-after-jgit-4-different-timestamps-features.png, server-before-after-jgit-dirty-workspace-upversioned-features.png, server-before-after-jgit-dirty-workspace-upversioned-plugin-with-change.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-314) Add default entry for 'Docker Hub' in the registry accounts [EBZ#496177]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-314?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston resolved ERT-314. ------------------------------- Fix Version/s: Neon.1 (4.6) Resolution: Done > Add default entry for 'Docker Hub' in the registry accounts [EBZ#496177] > ------------------------------------------------------------------------ > > Key: ERT-314 > URL: https://issues.jboss.org/browse/ERT-314 > Project: Eclipse Release Train > Issue Type: Enhancement > Components: Linux Tools > Reporter: Nick Boldt > Assignee: Jeff Johnston > Labels: Docker, bzira > Fix For: Neon.1 (4.6) > > > The registry will just contain the Server Address, so the user will have just to edit the settings to specify the credentials if he/she wants to push images. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3960) rename platform installer artifacts to start with "devsuite" instead of "development-suite"

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3960?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3960: -------------------------------- Fix Version/s: 10.0.1.AM2 > rename platform installer artifacts to start with "devsuite" instead of "development-suite" > ------------------------------------------------------------------------------------------- > > Key: JBDS-3960 > URL: https://issues.jboss.org/browse/JBDS-3960 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 10.0.1.AM2 > > > Max said: "I don't see dev studio in that download dialog - I see "Development-suite" ...which btw. is wrong, it should be devsuite here. Have you opened bug for this already ?" > So, I've opened a bug for this, already. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2016