October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4549) DevSuite uninstaller fails when target location %ProgramFiles%\DevelopmentSuite

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4549?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4549: ----------------------------- Fix Version/s: 11.1.0.GA (was: 11.1.0.AM3) > DevSuite uninstaller fails when target location %ProgramFiles%\DevelopmentSuite > ------------------------------------------------------------------------------- > > Key: JBDS-4549 > URL: https://issues.jboss.org/browse/JBDS-4549 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.1.0.AM2 > Reporter: Sudhir Verma > Assignee: Sudhir Verma > Fix For: 11.1.0.GA > > > Installation into 'c:\Program Files\DevelopmentSuite' is supported by all components, but uninstaller fails to remove target install folder in this case. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24243) migrate Fuse Tools builds to JBT infrastructure/process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24243?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24243: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.5.x* > migrate Fuse Tools builds to JBT infrastructure/process > ------------------------------------------------------- > > Key: JBIDE-24243 > URL: https://issues.jboss.org/browse/JBIDE-24243 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, fusetools, updatesite > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.x > > > Fuse Tooling currently has jobs under this view: https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... > * https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/staging/builds/integration-stac... > ** https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/integration/updates/integration... > which publish integration, development or stable update sites. > As part of the migration of Fuse Tooling into JBoss Tools 4.5 for Oxygen, this path will change to something like: > * http://download.jboss.org/jbosstools/*oxygen*/snapshots/builds/fuse-tooling/ > * http://download.jboss.org/jbosstools/*oxygen*/staging/updates/fuse-tooling/ > We will also need to ensure that JBT composites/aggregates are configured to pick up these features/plugins. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4556) Deselecting components will always deselect items they depend on

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4556?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4556: ----------------------------- Fix Version/s: 11.x (was: 11.1.0.AM3) > Deselecting components will always deselect items they depend on > ---------------------------------------------------------------- > > Key: JBDS-4556 > URL: https://issues.jboss.org/browse/JBDS-4556 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.1.0.AM2 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 11.x > > > To put this into some understandable language: > - say I select devstudio > - then I select fuse tools, which depends on devstudio > - then I deselect fuse tools and suddenly devstudio is deselected > This principle works nicely when you select & deselect items when the dependencies have not been selected beforehand. But it is a bit of pain when they have. > Is there a way to differentiate between the case when the user actively selects the dependency, and when it is selected automatically? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4556) Deselecting components will always deselect items they depend on

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4556?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4556: ---------------------------------- [checkUnresolvedIssues.py] Slip to fixversion = *11.x* > Deselecting components will always deselect items they depend on > ---------------------------------------------------------------- > > Key: JBDS-4556 > URL: https://issues.jboss.org/browse/JBDS-4556 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.1.0.AM2 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 11.x > > > To put this into some understandable language: > - say I select devstudio > - then I select fuse tools, which depends on devstudio > - then I deselect fuse tools and suddenly devstudio is deselected > This principle works nicely when you select & deselect items when the dependencies have not been selected beforehand. But it is a bit of pain when they have. > Is there a way to differentiate between the case when the user actively selects the dependency, and when it is selected automatically? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24491: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.1.AM3) > CDK Server adapter: allow users to look up the address of the docker registry > ----------------------------------------------------------------------------- > > Key: JBIDE-24491 > URL: https://issues.jboss.org/browse/JBIDE-24491 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.5.x > > > if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry. > When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address. > Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code} > It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line. > I dont know yet how to look it up for the OpenShift online variant though. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24491: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.5.x* > CDK Server adapter: allow users to look up the address of the docker registry > ----------------------------------------------------------------------------- > > Key: JBIDE-24491 > URL: https://issues.jboss.org/browse/JBIDE-24491 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.5.x > > > if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry. > When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address. > Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code} > It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line. > I dont know yet how to look it up for the OpenShift online variant though. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24243) migrate Fuse Tools builds to JBT infrastructure/process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24243?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24243: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.1.AM3) > migrate Fuse Tools builds to JBT infrastructure/process > ------------------------------------------------------- > > Key: JBIDE-24243 > URL: https://issues.jboss.org/browse/JBIDE-24243 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, fusetools, updatesite > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.x > > > Fuse Tooling currently has jobs under this view: https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... > * https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/staging/builds/integration-stac... > ** https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/integration/updates/integration... > which publish integration, development or stable update sites. > As part of the migration of Fuse Tooling into JBoss Tools 4.5 for Oxygen, this path will change to something like: > * http://download.jboss.org/jbosstools/*oxygen*/snapshots/builds/fuse-tooling/ > * http://download.jboss.org/jbosstools/*oxygen*/staging/updates/fuse-tooling/ > We will also need to ensure that JBT composites/aggregates are configured to pick up these features/plugins. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24766) verify correct copyright dates, terms and licenses

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24766?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24766: ------------------------------- Fix Version/s: 4.5.1.Final (was: 4.5.1.AM3) > verify correct copyright dates, terms and licenses > -------------------------------------------------- > > Key: JBIDE-24766 > URL: https://issues.jboss.org/browse/JBIDE-24766 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools, fusetools-extras > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.1.Final > > Attachments: fuse_feature_info.png, fuse_installed_software.png > > > Verify the following are true: > * plugins should have the updated license terms/address: "General Counsel, 100 East Davie St., Raleigh NC 27601 USA" - see https://github.com/jbosstools/jbosstools-base/blob/master/foundation/feat... > * copyrights should state Red Hat, Inc. and others., with current date, and EPL 1.0 license (unless it's another license?) - see https://github.com/jbosstools/jbosstools-base/blob/master/foundation/feat... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24763) Some server itests are failing on Jenkins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24763?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24763: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.1.AM3) > Some server itests are failing on Jenkins > ----------------------------------------- > > Key: JBIDE-24763 > URL: https://issues.jboss.org/browse/JBIDE-24763 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.x > > Attachments: server-itests.png > > > Here's the job: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Currently we got around 30 failures: > {code} > All Failed Tests > Test Name > Duration > Age > org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[1] 5.3 sec 1 > org.jboss.tools.as.management.itests.AS7ManagerIntegrationTest.canGetServerState[7] 76 ms 1 > org.jboss.tools.as.ui.bot.itests.parametized.server.RuntimeDetectionDuplicatesTest.duplicateRuntimes default [0] 17 sec 1 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[4] 1.7 sec 2 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[4] 5.3 sec 2 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[1] 2.3 sec 3 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[0] 4.4 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[1] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[2] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[3] 2.2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[4] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[5] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[6] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[7] 2.3 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[8] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[9] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[10] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[11] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[12] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[13] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[14] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[15] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[16] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[17] 2 sec 6 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[0] 1.7 sec 6 > org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [0] 1 min 49 sec 6 > org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [1] 1 min 43 sec 6 > org.jboss.tools.wtp.runtimes.tomcat.itests.ServerUtilTest.testUniqueServerName 2.6 sec 6 > org.jboss.tools.wtp.runtimes.tomcat.itests.TomcatDetectionTest.testTomcatDetection 0.13 sec 6 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[2] 1.7 sec 7 > {code} > Nick already shared some details in JBIDE-22799 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24763) Some server itests are failing on Jenkins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24763?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24763: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.5.x* > Some server itests are failing on Jenkins > ----------------------------------------- > > Key: JBIDE-24763 > URL: https://issues.jboss.org/browse/JBIDE-24763 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.x > > Attachments: server-itests.png > > > Here's the job: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Currently we got around 30 failures: > {code} > All Failed Tests > Test Name > Duration > Age > org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[1] 5.3 sec 1 > org.jboss.tools.as.management.itests.AS7ManagerIntegrationTest.canGetServerState[7] 76 ms 1 > org.jboss.tools.as.ui.bot.itests.parametized.server.RuntimeDetectionDuplicatesTest.duplicateRuntimes default [0] 17 sec 1 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[4] 1.7 sec 2 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[4] 5.3 sec 2 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[1] 2.3 sec 3 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[0] 4.4 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[1] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[2] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[3] 2.2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[4] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[5] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[6] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[7] 2.3 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[8] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[9] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[10] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[11] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[12] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[13] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[14] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[15] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[16] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[17] 2 sec 6 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[0] 1.7 sec 6 > org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [0] 1 min 49 sec 6 > org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [1] 1 min 43 sec 6 > org.jboss.tools.wtp.runtimes.tomcat.itests.ServerUtilTest.testUniqueServerName 2.6 sec 6 > org.jboss.tools.wtp.runtimes.tomcat.itests.TomcatDetectionTest.testTomcatDetection 0.13 sec 6 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[2] 1.7 sec 7 > {code} > Nick already shared some details in JBIDE-22799 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 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 October 2017