June 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 updated JBIDE-22578: -------------------------------- Fix Version/s: 4.4.1.Alpha1 > 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: Critical > Fix For: 4.4.1.Alpha1 > > > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-22549) "Result" dialog enhancements

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22549?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-22549: ----------------------------------- Assignee: Rob Stryker Resolution: Done pushed to master > "Result" dialog enhancements > ---------------------------- > > Key: JBIDE-22549 > URL: https://issues.jboss.org/browse/JBIDE-22549 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.4.0.Final > Reporter: Xavier Coulon > Assignee: Rob Stryker > Fix For: 4.4.1.Alpha1 > > Attachments: Screenshot 2016-06-07 11.35.28.png > > > When executing a JMX remote operation, the "Result" dialog displays a single column that cannot be expanded, and the row content cannot be copied into the clipboard. > See the attached screenshot for visual explanations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22549) "Result" dialog enhancements

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22549?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22549: -------------------------------- Fix Version/s: 4.4.1.Alpha1 > "Result" dialog enhancements > ---------------------------- > > Key: JBIDE-22549 > URL: https://issues.jboss.org/browse/JBIDE-22549 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.4.0.Final > Reporter: Xavier Coulon > Fix For: 4.4.1.Alpha1 > > Attachments: Screenshot 2016-06-07 11.35.28.png > > > When executing a JMX remote operation, the "Result" dialog displays a single column that cannot be expanded, and the row content cannot be copied into the clipboard. > See the attached screenshot for visual explanations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22501) CDK stuck on Starting... after launch

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22501?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22501: ------------------------------------- [~mmalina] I really haven't seen it :( I've been over the code a number of times and haven't seen anything. I vaguely recall the poller not being fired on some occasion, but I think that might have not been cdk and was other server adapters. So really I don't know. Things that *could* cause such a problem are either the poller not being launched, or the poller not working as expected (such as running vagrant global-status and getting an error, or incorrectly parsing the output), but the code seems to handle these cases properly and as expected. I'm going to close this issue for now, but I'll remember it this time in case I see something similar. > CDK stuck on Starting... after launch > ------------------------------------- > > Key: JBIDE-22501 > URL: https://issues.jboss.org/browse/JBIDE-22501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.0.Final > > > This happened to me a few times and I think I mentioned it in a JIRA, but AFAIK there is no separate JIRA for this. > This is what I did today (verifying JBDS-3739): > 1. Start my Eclipse Neon RC2 > 2. Updated Eclipse > 3. Updated Docker Tools to latest nightly > 4. Installed nightly JBoss Tools Abridged > 5. Set up cdk server (CDK 2.0 on my disk, already set up and started several times before) > 6. Start CDK server > Everything fine here - after some time it's Started, I accepted the OpenShift cert, Docker connection worked. > 7. Stop CDK server > 8. Start CDK server > This time it's stuck on Starting... even though I can see from the console that the vagrant box started: > {code} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Clearing any previously set forwarded ports... > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 (guest) => 2222 (host) (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Remote connection disconnect. Retrying... > ==> default: Machine booted and ready! > ==> default: Checking for guest additions in VM... > default: No guest additions were detected on the base box for this VM! Guest > default: additions are required for forwarded ports, shared folders, host only > default: networking, and more. If SSH fails on this machine, please install > default: the guest additions and repackage the box to continue. > default: > default: This is not an error message; everything may continue to work properly, > default: in which case you may ignore this message. > ==> default: Configuring and enabling network interfaces... > ==> default: Registering box with vagrant-registration... > ==> default: Copying TLS certificates to /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > ==> default: Rsyncing folder: /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/ => /vagrant > ==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision` > ==> default: flag to force provisioning. Provisioners marked to run always will still run. > {code} > Now it will probably time out and stop the server. And most probably next start will work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22501) CDK stuck on Starting... after launch

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22501?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-22501. --------------------------------- Fix Version/s: 4.4.0.Final (was: 4.4.x) Resolution: Cannot Reproduce Bug > CDK stuck on Starting... after launch > ------------------------------------- > > Key: JBIDE-22501 > URL: https://issues.jboss.org/browse/JBIDE-22501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.0.Final > > > This happened to me a few times and I think I mentioned it in a JIRA, but AFAIK there is no separate JIRA for this. > This is what I did today (verifying JBDS-3739): > 1. Start my Eclipse Neon RC2 > 2. Updated Eclipse > 3. Updated Docker Tools to latest nightly > 4. Installed nightly JBoss Tools Abridged > 5. Set up cdk server (CDK 2.0 on my disk, already set up and started several times before) > 6. Start CDK server > Everything fine here - after some time it's Started, I accepted the OpenShift cert, Docker connection worked. > 7. Stop CDK server > 8. Start CDK server > This time it's stuck on Starting... even though I can see from the console that the vagrant box started: > {code} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Clearing any previously set forwarded ports... > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 (guest) => 2222 (host) (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Remote connection disconnect. Retrying... > ==> default: Machine booted and ready! > ==> default: Checking for guest additions in VM... > default: No guest additions were detected on the base box for this VM! Guest > default: additions are required for forwarded ports, shared folders, host only > default: networking, and more. If SSH fails on this machine, please install > default: the guest additions and repackage the box to continue. > default: > default: This is not an error message; everything may continue to work properly, > default: in which case you may ignore this message. > ==> default: Configuring and enabling network interfaces... > ==> default: Registering box with vagrant-registration... > ==> default: Copying TLS certificates to /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > ==> default: Rsyncing folder: /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/ => /vagrant > ==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision` > ==> default: flag to force provisioning. Provisioners marked to run always will still run. > {code} > Now it will probably time out and stop the server. And most probably next start will work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3936) devstudio.exe has eclipse icon

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3936?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3936: --------------------------------- Labels: respin-b (was: respin-a) > devstudio.exe has eclipse icon > ------------------------------ > > Key: JBDS-3936 > URL: https://issues.jboss.org/browse/JBDS-3936 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.0.0.GA > Reporter: Radim Hopp > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-b > Fix For: 10.0.0.GA > > Attachments: devstudio.ico.10.png, jbds.ico.9.1.png, jbds.ico.9.1export-layers.png, jbds.ico_vs_devstudio.ico.png > > > [installFolder]/studio/devstudio.exe has eclipse icon instead of redhat developer icon. > http://i.imgur.com/ZKjeJGC.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3941) use new logo in UI of Development Suite installer

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3941?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3941: ----------------------------- > use new logo in UI of Development Suite installer > ------------------------------------------------- > > Key: JBDS-3941 > URL: https://issues.jboss.org/browse/JBDS-3941 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Catherine Robson > Priority: Critical > Labels: havoc > Fix For: 10.0.0.GA > > Attachments: installer-new-logo-confirmation.png, installer-new-logo-login.png, logo_RHDP.svg, RedHatDeveloperStudio_Logo_Installer.ico > > > Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3941) use new logo in UI of Development Suite installer

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3941?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3941: --------------------------------- Component/s: platform-installer (was: installer) > use new logo in UI of Development Suite installer > ------------------------------------------------- > > Key: JBDS-3941 > URL: https://issues.jboss.org/browse/JBDS-3941 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Catherine Robson > Priority: Critical > Labels: havoc > Fix For: 10.0.0.GA > > Attachments: installer-new-logo-confirmation.png, installer-new-logo-login.png, logo_RHDP.svg, RedHatDeveloperStudio_Logo_Installer.ico > > > Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Alexey Kazakov resolved JBDS-3739. ---------------------------------- Resolution: Done Resolving. > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Xavier Coulon > Priority: Blocker > Labels: havoc > Fix For: 10.0.0.GA > > Attachments: docker-frozen.txt > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3941) use new logo in UI of Development Suite installer

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3941?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3941: -------------------------------------- [~sjcox] that new logo for the installer looks weird. We renamed Red Hat Developer Platform to Red Hat Developer Suite. We used the RHD logo as a visual reference to RHD program. Which is incorrect as I understand. But we can't replace it by Red Hat Developer Platform because we don't use this name for this release. So we need to use Red Hat Developer Suite instead or use something else. [~dgolovin] will provide a screenshot later to give you an idea when we use it in the installer. > use new logo in UI of Development Suite installer > ------------------------------------------------- > > Key: JBDS-3941 > URL: https://issues.jboss.org/browse/JBDS-3941 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Catherine Robson > Priority: Critical > Labels: havoc > Fix For: 10.0.0.GA > > Attachments: installer-new-logo-confirmation.png, installer-new-logo-login.png, logo_RHDP.svg, RedHatDeveloperStudio_Logo_Installer.ico > > > Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016