April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22033) Stopping the OpenShift server doesn't terminate the remote debugger

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22033?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22033. --------------------------------- Verified on nightly build of JBT with OpenShift plugin build B260. > Stopping the OpenShift server doesn't terminate the remote debugger > ------------------------------------------------------------------- > > Key: JBIDE-22033 > URL: https://issues.jboss.org/browse/JBIDE-22033 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.1.CR1 > > > When stopping an openshift server, the remote debugger should be terminated as well. It is not. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3736) Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3736?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3736. ----------------------------- Using today's installer (B32) it created the server silently - so verified, and closing. > Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3736 > URL: https://issues.jboss.org/browse/JBDS-3736 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Rob Stryker > Fix For: 9.1.0.CR1 > > > Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent. The CDK, however, is reported to the user as a newly found runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3756) Have a single progress bar for the installer

by Pete Muir (JIRA)

Pete Muir created JBDS-3756: ------------------------------- Summary: Have a single progress bar for the installer Key: JBDS-3756 URL: https://issues.jboss.org/browse/JBDS-3756 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: installer Reporter: Pete Muir Priority: Minor Most installers have a single progress bar that shows the overall progress, and then text which explains which component is being installed right now. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-628) JBTIS composite sites contains 3 or 4 copies of the same IUs, and up to 3 different versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-628?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-628: ----------------------------- Attachment: 3-copies-of-comm.proj.examples_GA.png 4-copies-of-comm.proj.examples_EA.png > JBTIS composite sites contains 3 or 4 copies of the same IUs, and up to 3 different versions > -------------------------------------------------------------------------------------------- > > Key: JBTIS-628 > URL: https://issues.jboss.org/browse/JBTIS-628 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Attachments: 3-copies-of-comm.proj.examples_GA.png, 4-copies-of-comm.proj.examples_EA.png > > > {quote} > Might be nothing but the p2director install tests [1] failed on multiple org.jboss.tools.community.project.examples being defined: > 16:55:46 INSTALL FAILED > 16:55:46 > 16:55:46 [p2.dir] Installing tern-server-nodejs-feature.feature.group 1.1.0.201511082254. > 16:55:46 [p2.dir] Cannot complete the install because of a conflicting dependency. > 16:55:46 [p2.dir] Software being installed: JBoss Tools Community Project Examples 3.0.1.CR1-v20160324-1911-B99 (org.jboss.tools.community.project.examples.feature.feature.group 3.0.1.CR1-v20160324-1911-B99) > 16:55:46 [p2.dir] Software being installed: JBoss Tools Community Project Examples Developer Resources 3.0.1.Beta2-v20160121-2329-B74 (org.jboss.tools.community.project.examples.feature.source.feature.group 3.0.1.Beta2-v20160121-2329-B74) > 16:55:46 [p2.dir] Only one of the following can be installed at once: > 16:55:46 [p2.dir] JBoss Tools Community Project Examples 3.0.1.Beta2-v20160121-2329-B74 (org.jboss.tools.community.project.examples 3.0.1.Beta2-v20160121-2329-B74) > 16:55:46 [p2.dir] JBoss Tools Community Project Examples 3.0.0.Final-v20151001-1531-B45 (org.jboss.tools.community.project.examples 3.0.0.Final-v20151001-1531-B45) > I'm pulling in version 3.0.1.CR1 here: > https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > --paull > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p... > {quote} > Reason for this failure is that you're pulling from TWO versions of JBT: > * 3.0.1.Beta2-v20160121-2329-B74 > * 3.0.0.Final-v20151001-1531-B45 > You should only be pulling from ONE. > Your composites have 3 or 4 different copies of the same features. And of those, there are 3 different VERSIONS. See screenshots. This is terribly wrong. You should only need to include a single version, and don't need to include 3-4 copies. > Here are the URLs used by your install test job: > http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-s... > http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-s... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-628) JBTIS composite sites contains 3 or 4 copies of the same IUs, and up to 3 different versions

by Nick Boldt (JIRA)

Nick Boldt created JBTIS-628: -------------------------------- Summary: JBTIS composite sites contains 3 or 4 copies of the same IUs, and up to 3 different versions Key: JBTIS-628 URL: https://issues.jboss.org/browse/JBTIS-628 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 4.3.0.CR1 Reporter: Nick Boldt {quote} Might be nothing but the p2director install tests [1] failed on multiple org.jboss.tools.community.project.examples being defined: 16:55:46 INSTALL FAILED 16:55:46 16:55:46 [p2.dir] Installing tern-server-nodejs-feature.feature.group 1.1.0.201511082254. 16:55:46 [p2.dir] Cannot complete the install because of a conflicting dependency. 16:55:46 [p2.dir] Software being installed: JBoss Tools Community Project Examples 3.0.1.CR1-v20160324-1911-B99 (org.jboss.tools.community.project.examples.feature.feature.group 3.0.1.CR1-v20160324-1911-B99) 16:55:46 [p2.dir] Software being installed: JBoss Tools Community Project Examples Developer Resources 3.0.1.Beta2-v20160121-2329-B74 (org.jboss.tools.community.project.examples.feature.source.feature.group 3.0.1.Beta2-v20160121-2329-B74) 16:55:46 [p2.dir] Only one of the following can be installed at once: 16:55:46 [p2.dir] JBoss Tools Community Project Examples 3.0.1.Beta2-v20160121-2329-B74 (org.jboss.tools.community.project.examples 3.0.1.Beta2-v20160121-2329-B74) 16:55:46 [p2.dir] JBoss Tools Community Project Examples 3.0.0.Final-v20151001-1531-B45 (org.jboss.tools.community.project.examples 3.0.0.Final-v20151001-1531-B45) I'm pulling in version 3.0.1.CR1 here: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... --paull [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p... {quote} Reason for this failure is that you're pulling from TWO versions of JBT: * 3.0.1.Beta2-v20160121-2329-B74 * 3.0.0.Final-v20151001-1531-B45 You should only be pulling from ONE. Your composites have 3 or 4 different copies of the same features. And of those, there are 3 different VERSIONS. See screenshots. This is terribly wrong. You should only need to include a single version, and don't need to include 3-4 copies. Here are the URLs used by your install test job: http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-s... http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-s... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-627) JBTIS composite site missing child site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-627?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-627: ----------------------------- Attachment: missing-child-sites.png > JBTIS composite site missing child site > --------------------------------------- > > Key: JBTIS-627 > URL: https://issues.jboss.org/browse/JBTIS-627 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Reporter: Nick Boldt > Fix For: 4.3.0.CR1 > > Attachments: missing-child-sites.png > > > If I look at the two sites [1], [2] from which the install test is pulling content (using p2 browser)... > [1] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-s... > [2] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-s... > I see there are missing URLs in the composites: > "Missing http://download.jboss.org/jbosstools/mars/integration/updates/integration..." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21992) Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21992?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21992. --------------------------------- Verified on nightly build of JBT with OpenShift plugin build B260. > Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues > --------------------------------------------------------------------------------------------- > > Key: JBIDE-21992 > URL: https://issues.jboss.org/browse/JBIDE-21992 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: deploy_docker_wizard > Fix For: 4.3.1.CR1 > > Attachments: deploy-config-scalability-page.png, deployment-config-page.png, DeploymentConfigLayout.png > > > The ""Deployment Configuration & Scalability" wizard page when deploying a docker image has minor UI glitches that we should fix as you can see in the following screenshot. We should also maybe use 3 groups to distinguish the 3 settings cathegories in more obvious way. > !deploy-config-scalability-page.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-627) JBTIS composite site missing child site

by Nick Boldt (JIRA)

Nick Boldt created JBTIS-627: -------------------------------- Summary: JBTIS composite site missing child site Key: JBTIS-627 URL: https://issues.jboss.org/browse/JBTIS-627 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Reporter: Nick Boldt Fix For: 4.3.0.CR1 If I look at the two sites [1], [2] from which the install test is pulling content (using p2 browser)... [1] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-s... [2] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-s... I see there are missing URLs in the composites: "Missing http://download.jboss.org/jbosstools/mars/integration/updates/integration..." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3693) JBDS instal should be running with -DTRACE=true and output redirected to instal.log file

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3693?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3693. ----------------------------- Verified with B32, closing. > JBDS instal should be running with -DTRACE=true and output redirected to instal.log file > ---------------------------------------------------------------------------------------- > > Key: JBDS-3693 > URL: https://issues.jboss.org/browse/JBDS-3693 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.CR1 > > > Have detailed log for JBDS installation is required to fix possible JBDS installation issues. JBDS installation log should be redirected to install.log file or jbds.log file. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3734) When using existing install for vagrant VAGRANT_DETECTED_OS=cygwin should be set in user evironment

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3734?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3734. ----------------------------- Verified with B32, closing. > When using existing install for vagrant VAGRANT_DETECTED_OS=cygwin should be set in user evironment > --------------------------------------------------------------------------------------------------- > > Key: JBDS-3734 > URL: https://issues.jboss.org/browse/JBDS-3734 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > move VAGRANT_DETECTED_OS=cygwin to setUp part of vagrant installation -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 April 2016