June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22583) org.jboss.tools.openshift.cdk.server.test depends on org.jboss.tools.openshift.core 3.3.0 but only 3.2.0 is available in 4.4.0.x branch

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22583?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22583: ----------------------------------- Issue Type: Bug (was: Feature Request) > org.jboss.tools.openshift.cdk.server.test depends on org.jboss.tools.openshift.core 3.3.0 but only 3.2.0 is available in 4.4.0.x branch > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22583 > URL: https://issues.jboss.org/browse/JBIDE-22583 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.4.0.Final > > > {code} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.tools.openshift.cdk.server.test 3.2.0.qualifier > [ERROR] Missing requirement: org.jboss.tools.openshift.cdk.server.test 3.2.0.qualifier requires 'bundle org.jboss.tools.openshift.core 3.3.0' but it could not be found > [ERROR] > [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help. > [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.openshift.tests:org.jboss.tools.openshift.cdk.server.test:3.2.0-SNAPSHOT @ /mnt/hudson_workspace/workspace/jbosstools-openshift_4.4.neon/sources/tests/org.jboss.tools.openshift.cdk.server.test/pom.xml: See log for details -> [Help 1] > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_... > Solution: https://github.com/jbosstools/jbosstools-openshift/pull/1220 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22583) org.jboss.tools.openshift.cdk.server.test depends on org.jboss.tools.openshift.core 3.3.0 but only 3.2.0 is available in 4.4.0.x branch

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22583?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-22583: ---------------------------------- Assignee: Fred Bricon > org.jboss.tools.openshift.cdk.server.test depends on org.jboss.tools.openshift.core 3.3.0 but only 3.2.0 is available in 4.4.0.x branch > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22583 > URL: https://issues.jboss.org/browse/JBIDE-22583 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.4.0.Final > > > {code} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.tools.openshift.cdk.server.test 3.2.0.qualifier > [ERROR] Missing requirement: org.jboss.tools.openshift.cdk.server.test 3.2.0.qualifier requires 'bundle org.jboss.tools.openshift.core 3.3.0' but it could not be found > [ERROR] > [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help. > [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.openshift.tests:org.jboss.tools.openshift.cdk.server.test:3.2.0-SNAPSHOT @ /mnt/hudson_workspace/workspace/jbosstools-openshift_4.4.neon/sources/tests/org.jboss.tools.openshift.cdk.server.test/pom.xml: See log for details -> [Help 1] > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_... > Solution: https://github.com/jbosstools/jbosstools-openshift/pull/1220 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22583) org.jboss.tools.openshift.cdk.server.test depends on org.jboss.tools.openshift.core 3.3.0 but only 3.2.0 is available in 4.4.0.x branch

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22583?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22583: ------------------------------- Description: {code} [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: org.jboss.tools.openshift.cdk.server.test 3.2.0.qualifier [ERROR] Missing requirement: org.jboss.tools.openshift.cdk.server.test 3.2.0.qualifier requires 'bundle org.jboss.tools.openshift.core 3.3.0' but it could not be found [ERROR] [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help. [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.openshift.tests:org.jboss.tools.openshift.cdk.server.test:3.2.0-SNAPSHOT @ /mnt/hudson_workspace/workspace/jbosstools-openshift_4.4.neon/sources/tests/org.jboss.tools.openshift.cdk.server.test/pom.xml: See log for details -> [Help 1] {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_... Solution: https://github.com/jbosstools/jbosstools-openshift/pull/1220 was: {code} [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: org.jboss.tools.openshift.cdk.server.test 3.2.0.qualifier [ERROR] Missing requirement: org.jboss.tools.openshift.cdk.server.test 3.2.0.qualifier requires 'bundle org.jboss.tools.openshift.core 3.3.0' but it could not be found [ERROR] [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help. [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.openshift.tests:org.jboss.tools.openshift.cdk.server.test:3.2.0-SNAPSHOT @ /mnt/hudson_workspace/workspace/jbosstools-openshift_4.4.neon/sources/tests/org.jboss.tools.openshift.cdk.server.test/pom.xml: See log for details -> [Help 1] {code} > org.jboss.tools.openshift.cdk.server.test depends on org.jboss.tools.openshift.core 3.3.0 but only 3.2.0 is available in 4.4.0.x branch > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22583 > URL: https://issues.jboss.org/browse/JBIDE-22583 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Final > > > {code} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.tools.openshift.cdk.server.test 3.2.0.qualifier > [ERROR] Missing requirement: org.jboss.tools.openshift.cdk.server.test 3.2.0.qualifier requires 'bundle org.jboss.tools.openshift.core 3.3.0' but it could not be found > [ERROR] > [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help. > [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.openshift.tests:org.jboss.tools.openshift.cdk.server.test:3.2.0-SNAPSHOT @ /mnt/hudson_workspace/workspace/jbosstools-openshift_4.4.neon/sources/tests/org.jboss.tools.openshift.cdk.server.test/pom.xml: See log for details -> [Help 1] > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_... > Solution: https://github.com/jbosstools/jbosstools-openshift/pull/1220 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22583) org.jboss.tools.openshift.cdk.server.test depends on org.jboss.tools.openshift.core 3.3.0 but only 3.2.0 is available in 4.4.0.x branch

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22583?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22583: ------------------------------- Fix Version/s: 4.4.0.Final > org.jboss.tools.openshift.cdk.server.test depends on org.jboss.tools.openshift.core 3.3.0 but only 3.2.0 is available in 4.4.0.x branch > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22583 > URL: https://issues.jboss.org/browse/JBIDE-22583 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.4.0.Final > > > {code} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.tools.openshift.cdk.server.test 3.2.0.qualifier > [ERROR] Missing requirement: org.jboss.tools.openshift.cdk.server.test 3.2.0.qualifier requires 'bundle org.jboss.tools.openshift.core 3.3.0' but it could not be found > [ERROR] > [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help. > [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.openshift.tests:org.jboss.tools.openshift.cdk.server.test:3.2.0-SNAPSHOT @ /mnt/hudson_workspace/workspace/jbosstools-openshift_4.4.neon/sources/tests/org.jboss.tools.openshift.cdk.server.test/pom.xml: See log for details -> [Help 1] > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_... > Solution: https://github.com/jbosstools/jbosstools-openshift/pull/1220 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22583) org.jboss.tools.openshift.cdk.server.test depends on org.jboss.tools.openshift.core 3.3.0 but only 3.2.0 is available in 4.4.0.x branch

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-22583: ---------------------------------- Summary: org.jboss.tools.openshift.cdk.server.test depends on org.jboss.tools.openshift.core 3.3.0 but only 3.2.0 is available in 4.4.0.x branch Key: JBIDE-22583 URL: https://issues.jboss.org/browse/JBIDE-22583 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.4.0.Final Reporter: Nick Boldt Priority: Blocker {code} [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: org.jboss.tools.openshift.cdk.server.test 3.2.0.qualifier [ERROR] Missing requirement: org.jboss.tools.openshift.cdk.server.test 3.2.0.qualifier requires 'bundle org.jboss.tools.openshift.core 3.3.0' but it could not be found [ERROR] [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help. [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.openshift.tests:org.jboss.tools.openshift.cdk.server.test:3.2.0-SNAPSHOT @ /mnt/hudson_workspace/workspace/jbosstools-openshift_4.4.neon/sources/tests/org.jboss.tools.openshift.cdk.server.test/pom.xml: See log for details -> [Help 1] {code} -- 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 Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3941?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3941: ------------------------------------- [~crobson], [~sjcox] updated Installer JBDS 9 Icon and new logo, below is final design, does it look right? !new-new-branding.png! !screenshot-1.png! > 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, new-new-branding.png, RedHatDeveloperStudio_Logo_Installer.ico, screenshot-1.png > > > 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 Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3941?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3941: -------------------------------- Attachment: screenshot-1.png > 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, new-new-branding.png, RedHatDeveloperStudio_Logo_Installer.ico, screenshot-1.png > > > 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 Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3941?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3941: -------------------------------- Attachment: new-new-branding.png > 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, new-new-branding.png, 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-3942) Document (and verify) the current operation of the platform installer

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3942?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-3942: --------------------------------- Thanks for the cc, [~ldimaggio]. I'll add a link here for the document part when this doc is ready for review. > Document (and verify) the current operation of the platform installer > ---------------------------------------------------------------------- > > Key: JBDS-3942 > URL: https://issues.jboss.org/browse/JBDS-3942 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Len DiMaggio > Priority: Critical > Fix For: 10.0.0.GA > > > We have to be careful to test and document the operation of the installer for the release: > Component detection as performed that the bundled platform installer has recently changed. It's important that we communicate clearly to our users how this detection is functioning as of today, and what their options are for running the installer. > The installer installs these (6) high-level components: > * CDK > * Cygwin > * VirtialBox > * Vagrant > * JDK > * DevStudio > Topic: Component Detection Performed by The Installer: > As of today, the installer is able to detect these components: > * Java > * VirtualBox > * Vagrant > If a user runs the installer, and one of these detectable components is installed, the installer will verify that the version of the installed component is supported by the Developer Platform. > If the version of the detected component installed is not supported, an error will be reported to the user. The installer will not automatically update the detected installed component to a supported version. > If the version of the installed component is supported by the Developer Platform, the installer will not overwrite that installed component. > Topic: Components Auto-Selected by the Installer > If the installer is run on a system with none of the high level components pre-installed, the installer should have all components auto-selected to be installed. > Topic: Optionally Installing Components > As of today, users can choose to install selected components singly with the installer. The only dependency should be that if the user attempts to install DevStudio alone, the installer will require the user to also install the JDK at the same time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 updated JBIDE-22578: -------------------------------- Priority: Critical (was: Major) > 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

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