March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21386) Create and use Neon M5 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21386?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21386: ------------------------------- Attachment: p2diff.JBIDE-21386.txt p2diff.JBIDE-21386.summary.txt p2diff for the change to Central: [^p2diff.JBIDE-21386.txt] [^p2diff.JBIDE-21386.summary.txt] > Create and use Neon M5 target platform > -------------------------------------- > > Key: JBIDE-21386 > URL: https://issues.jboss.org/browse/JBIDE-21386 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: jbds-tp-p2diff-460-summary.txt, jbds-tp-p2diff-460.txt, jbt-tp-p2diff-460-summary.txt, jbt-tp-p2diff-460.txt, jbtcentral-p2diff_460.txt, p2diff.JBIDE-21386.summary.txt, p2diff.JBIDE-21386.txt > > > Prepare TP to use Neon M5 bits. Cloned from JBIDE-20976 so I can start a fresh issue. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > * jbt tp, > * jbds tp, > * central tp; > * jbt-build-sites, > * jbds site build; > * update install/matrix jobs to use new Eclipse JEE/platform binary; > * mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21847) Start port forwarding button is disabled after starting and stopping it

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21847?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21847: ---------------------------------- Description: In Port Forwarding wizard when I start port forwarding, then stop it, the button Start All is disabled and it is not possible to start port forwarding again. Well, both buttons after starting and stopping are disabled, only OK is enabled. (was: In Port Forwarding dialog when I start port forwarding, then stop it, the button Start All is disabled and it is not possible to start port forwarding again. Well, both buttons after starting and stopping are disabled, only OK is enabled.) > Start port forwarding button is disabled after starting and stopping it > ----------------------------------------------------------------------- > > Key: JBIDE-21847 > URL: https://issues.jboss.org/browse/JBIDE-21847 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3, port_forwarding_wizard > > In Port Forwarding wizard when I start port forwarding, then stop it, the button Start All is disabled and it is not possible to start port forwarding again. Well, both buttons after starting and stopping are disabled, only OK is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21847) Start port forwarding button is disabled after starting and stopping it

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21847?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21847: ---------------------------------- Workaround Description: Reopen Port Forwarding wizard. Workaround: Workaround Exists > Start port forwarding button is disabled after starting and stopping it > ----------------------------------------------------------------------- > > Key: JBIDE-21847 > URL: https://issues.jboss.org/browse/JBIDE-21847 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3, port_forwarding_wizard > > In Port Forwarding wizard when I start port forwarding, then stop it, the button Start All is disabled and it is not possible to start port forwarding again. Well, both buttons after starting and stopping are disabled, only OK is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21847) Start port forwarding button is disabled after starting and stopping it

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21847: ------------------------------------- Summary: Start port forwarding button is disabled after starting and stopping it Key: JBIDE-21847 URL: https://issues.jboss.org/browse/JBIDE-21847 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda In Port Forwarding dialog when I start port forwarding, then stop it, the button Start All is disabled and it is not possible to start port forwarding again. Well, both buttons after starting and stopping are disabled, only OK is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21847) Start port forwarding button is disabled after starting and stopping it

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21847?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21847: ---------------------------------- Labels: openshift_v3 port_forwarding_wizard (was: ) > Start port forwarding button is disabled after starting and stopping it > ----------------------------------------------------------------------- > > Key: JBIDE-21847 > URL: https://issues.jboss.org/browse/JBIDE-21847 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3, port_forwarding_wizard > > In Port Forwarding dialog when I start port forwarding, then stop it, the button Start All is disabled and it is not possible to start port forwarding again. Well, both buttons after starting and stopping are disabled, only OK is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21847) Start port forwarding button is disabled after starting and stopping it

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21847?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21847: ---------------------------------- Steps to Reproduce: ASSERT: Have an OpenShift 3 application EXEC: Open Port Forwarding wizard. EXEC: Start port forwarding. EXEC: Stop port forwarding. RESULT: Start All and Stop All buttons are disabled. EXPECTED RESULT: Start All button is enabled and Stop All button is disabled. was: ASSERT: Have an OpenShift 3 application EXEC: Open Port Forwarding dialog. EXEC: Start port forwarding. EXEC: Stop port forwarding. RESULT: Start All and Stop All buttons are disabled. EXPECTED RESULT: Start All button is enabled and Stop All button is disabled. > Start port forwarding button is disabled after starting and stopping it > ----------------------------------------------------------------------- > > Key: JBIDE-21847 > URL: https://issues.jboss.org/browse/JBIDE-21847 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3, port_forwarding_wizard > > In Port Forwarding dialog when I start port forwarding, then stop it, the button Start All is disabled and it is not possible to start port forwarding again. Well, both buttons after starting and stopping are disabled, only OK is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21821) JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21821?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21821: ------------------------------------ Two versions in the same TP would be worse. We might want to replace the http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/mars/ with something that includes egit 4.1 ONLY (not egit 4.0). Having two versions would still allow both jgit 4.0 and 4.1 to be coinstalled and result in " Unable to resolve resource org.eclipse.egit.ui because it is exposed to package 'org.eclipse.jgit.transport' from resources org.eclipse.jgit 4.1.1.201511131810-r and org.eclipse.jgit 4.0.3.201509231615-r via two dependency chains." error above. > JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2 > ---------------------------------------------------------------- > > Key: JBIDE-21821 > URL: https://issues.jboss.org/browse/JBIDE-21821 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, marketplace > Reporter: Thomas Mäder > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: FrameworkEvent ERROR.txt, jbt-error, jgit40_41_JBDS.installed.txt, jgit40_41_JBT.installed.txt > > > Installing Red Hat JBoss Developer Studio 9.0.0GA into a fresh Eclipse 4.5.2 (for Eclipse Committers) causes Egit to break. > # Install Eclipse 4.5.2 > # In the Marketplace, search for "jboss developer studio" > # You get a single result: Red Hat JBoss Developer Studio 9.0.0 GA > # Install it > # Restart > # Observe: the EGit views and preferences are missing > # Observe: you get messages in the Eclipse error log concerning a dependency version incompatibility -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21821) JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21821?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21821: ---------------------------------------- org.eclipse.egit.ui.importer is not part of Eclipse IDE, and JBoss Tools seems to reference a version of this bundle that isn't compatible with the version of EGit in Mars.2. So it installs older EGit, and messes up some stuff. A workaround is problably to add http://download.eclipse.org/egit/updates-4.1.1/ as a visible site and to install newer version of the smart import support from there. As for a good solution, I believe we could consider releasing a target-platform with the 2 versions of this bundle if possible. > JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2 > ---------------------------------------------------------------- > > Key: JBIDE-21821 > URL: https://issues.jboss.org/browse/JBIDE-21821 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, marketplace > Reporter: Thomas Mäder > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: FrameworkEvent ERROR.txt, jbt-error, jgit40_41_JBDS.installed.txt, jgit40_41_JBT.installed.txt > > > Installing Red Hat JBoss Developer Studio 9.0.0GA into a fresh Eclipse 4.5.2 (for Eclipse Committers) causes Egit to break. > # Install Eclipse 4.5.2 > # In the Marketplace, search for "jboss developer studio" > # You get a single result: Red Hat JBoss Developer Studio 9.0.0 GA > # Install it > # Restart > # Observe: the EGit views and preferences are missing > # Observe: you get messages in the Eclipse error log concerning a dependency version incompatibility -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21821) JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21821?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21821: ------------------------------------ To further clarify why egit views disappear after installing JBT 4.3.0.Final: when you install JBoss Tools EGit Integration (or possibly something else in JBT?) it pulls in org.eclipse.egit.ui.importer_4.0.0 which depends on org.eclipse.jgit_4.0, available from our associateSite-liked default "last stable" target plaform [1]. (4.1 is NOT preinstalled in Eclipse JEE bundle, and is not on the Mars site, so p2 can't find a newer version to install 4.1 instead.) [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/mars/ So even if you've already got jgit 4.1 installed, you break your installation (egit stops working) because: {code} Bundle was not resolved because of a uses contraint violation. org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.egit.ui [osgi.identity; osgi.identity="org.eclipse.egit.ui"; type="osgi.bundle"; version:Version="4.1.1.201511131810-r"; singleton:="true"] because it is exposed to package 'org.eclipse.jgit.transport' from resources org.eclipse.jgit [osgi.identity; osgi.identity="org.eclipse.jgit"; type="osgi.bundle"; version:Version="4.1.1.201511131810-r"] and org.eclipse.jgit [osgi.identity; osgi.identity="org.eclipse.jgit"; type="osgi.bundle"; version:Version="4.0.3.201509231615-r"] via two dependency chains.{code} So by removing access to jgit 4.0 in the TP, we eliminate the second dependency chain. My workaround above was to uninstall org.jboss.tools.openshift.egit.integration.feature ("JBoss Tools EGit Integration") from the 4.3.1.CR1 site and reinstall it from a site which includes the 4.1 version of org.eclipse.egit.ui.importer. > JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2 > ---------------------------------------------------------------- > > Key: JBIDE-21821 > URL: https://issues.jboss.org/browse/JBIDE-21821 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, marketplace > Reporter: Thomas Mäder > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: FrameworkEvent ERROR.txt, jbt-error, jgit40_41_JBDS.installed.txt, jgit40_41_JBT.installed.txt > > > Installing Red Hat JBoss Developer Studio 9.0.0GA into a fresh Eclipse 4.5.2 (for Eclipse Committers) causes Egit to break. > # Install Eclipse 4.5.2 > # In the Marketplace, search for "jboss developer studio" > # You get a single result: Red Hat JBoss Developer Studio 9.0.0 GA > # Install it > # Restart > # Observe: the EGit views and preferences are missing > # Observe: you get messages in the Eclipse error log concerning a dependency version incompatibility -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21712) Deploy Latest fails when no replication controller exists

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21712?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21712. --------------------------------- Resolution: Done This seems to work now. > Deploy Latest fails when no replication controller exists > --------------------------------------------------------- > > Key: JBIDE-21712 > URL: https://issues.jboss.org/browse/JBIDE-21712 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Fix For: 4.3.1.CR1 > > > Deploying swarm-helloworld from https://github.com/burrsutter/cdk_helloworlds (see JBIDE-21698) doesn't trigger a deployment automatically. When doing Deploy Latest on the deployment config, an error is thrown: > {noformat} > Unable to perform a deployment for config swhello > Could not get resource swhello-0 in namespace toto: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "replicationControllers \"swhello-0\" not found", > "reason": "NotFound", > "details": { > "name": "swhello-0", > "kind": "replicationControllers" > }, > "code": 404 > } > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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