[JBoss JIRA] (JBIDE-21821) JBT 4.3.0.Final / JBDS 9.0.0.GA target platforms include org.eclipse.egit.importer.ui 4.0, which installs jgit 4.0; this breaks egit 4.1.1 views when JBT 4.3.0 or JBDS 9.0.0 are installed into Mars.2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21821?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-21821 at 3/14/16 12:52 PM:
--------------------------------------------------------------
PRs:
https://github.com/jbosstools/jbosstools-download.jboss.org/pull/595
https://github.com/jbdevstudio/jbdevstudio-website/pull/218/files?w=1
These will:
* remove mockup from /stable/JBIDE-21821 (already deleted from server too)
* put contents in staging - pushed live to server so you can test it
* put contents in stable - awaiting approval to push to server, obviously
Installation URLs:
http://download.jboss.org/jbosstools/mars/staging/updates/
https://devstudio.redhat.com/9.0/staging/updates/
was (Author: nickboldt):
PRs to:
* remove mockup from /stable/JBIDE-21821 (deleted from server too)
* put contents in staging - pushed live to server
* put contents in stable - awaiting approval
https://github.com/jbosstools/jbosstools-download.jboss.org/pull/595
https://github.com/jbdevstudio/jbdevstudio-website/pull/218/files?w=1
> JBT 4.3.0.Final / JBDS 9.0.0.GA target platforms include org.eclipse.egit.importer.ui 4.0, which installs jgit 4.0; this breaks egit 4.1.1 views when JBT 4.3.0 or JBDS 9.0.0 are installed into 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
> -----
> JBT 4.3.0.Final / JBDS 9.0.0.GA target platforms include org.eclipse.egit.importer.ui 4.0.0.201506090130-r (Mars.1 version), which installs jgit 4.0.3.201509231615-r (Mars.1 version); this breaks egit 4.1.1 views when installed into Mars.2, because Mars.2 site does not include org.eclipse.egit.ui.importer 4.1.1.201511131810-r, and you confuse egit when you have both jgit 4.0 and 4.1 installed, disabling views and preferences.
> Solution proposed is to add org.eclipse.egit.ui.importer 4.1.1.201511131810-r to the composite site from which JBT 4.3.0.Final and JBDS 9.0.0.GA are installed, so that when org.eclipse.egit.ui.importer is installed, p2 can select the 4.1.1 version instead of the 4.0.0 version.
> I would want to pull a mirror of http://download.eclipse.org/egit/updates-4.1.1/ onto download.jboss.org if we're cool with this solution.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21815) Image metadata not refreshed after name change
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21815?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-21815:
---------------------------------------
I confirm that this issue is still valid even after JBIDE-21776 and JBIDE-21626 were fixed.
> Image metadata not refreshed after name change
> ----------------------------------------------
>
> Key: JBIDE-21815
> URL: https://issues.jboss.org/browse/JBIDE-21815
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.3.1.CR1
>
>
> Steps to reproduce:
> - open the *Deploy Docker Image* wizard
> - input/search for {{jboss/infinispan-server:8.1.0.Final}}, then click on {{Next}}. The *Deploy Configuration & Scalability* page should show a handful of metadata, including {{INFINISPAN_VERSION = 8.1.0.Final}}
> - go back to the previous page, *Deploy an Image* and now input/search for {{jboss/wildfly:10.0.0.Final}} and click back on {{Next}} again.
> - ASSERT: the metadata should have been updated
> - FAILED: the metadata displayed correspond to the previously selected {{jboss/infinispan-server:8.1.0.Final}} Docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21701) Enable port forwarding on a given pod and a given debug port
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21701?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-21701:
-------------------------------------
Assignee: Fred Bricon (was: Xavier Coulon)
Pull request was updated with some tests.
> Enable port forwarding on a given pod and a given debug port
> ------------------------------------------------------------
>
> Key: JBIDE-21701
> URL: https://issues.jboss.org/browse/JBIDE-21701
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.3.1.CR1
>
>
> Given a remote debug port, we need to ensure to programmatically enable port forwarding on a pod, return the matching local debug port (named debug).
> The local port could be determined as the next available free port, or read from the server adapter's preferences. But that latter case would also require adding some UI to let a user set the local port. That could be done in a later iteration.
> If port forwarding is already enabled on the remote pod, then the current local debug port should be returned
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21828) OpenShift Explorer view flickers when refreshing a service
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-21828:
-------------------------------------
Assignee: Jeff Cantrill (was: Xavier Coulon)
> OpenShift Explorer view flickers when refreshing a service
> ----------------------------------------------------------
>
> Key: JBIDE-21828
> URL: https://issues.jboss.org/browse/JBIDE-21828
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Jeff Cantrill
> Fix For: 4.3.1.CR1
>
> Attachments: Screenshot 2016-03-08 10.32.39.png
>
>
> When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls.
> Adding some traces revealed 25 calls to {{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a service with a single pod.
> Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services.
> Custom/added logs in the console:
> {code}
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21821) JBT 4.3.0.Final / JBDS 9.0.0.GA target platforms include org.eclipse.egit.importer.ui 4.0, which installs jgit 4.0; this breaks egit 4.1.1 views when JBT 4.3.0 or JBDS 9.0.0 are installed into Mars.2
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21821?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-21821:
----------------------------------------
{quote} what is it in org.eclipse.egit.importer that forces 4.0.x version of jgit ? A limited version range{quote}
Yes, that's one rule of EGit, they want to avoid "hybrid" versions of their bundles, so the version ranges are tight. I didn't anticipate this issue at that time, so I didn't even try to negotiate for a wider range. Too bad.
> JBT 4.3.0.Final / JBDS 9.0.0.GA target platforms include org.eclipse.egit.importer.ui 4.0, which installs jgit 4.0; this breaks egit 4.1.1 views when JBT 4.3.0 or JBDS 9.0.0 are installed into 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
> -----
> JBT 4.3.0.Final / JBDS 9.0.0.GA target platforms include org.eclipse.egit.importer.ui 4.0.0.201506090130-r (Mars.1 version), which installs jgit 4.0.3.201509231615-r (Mars.1 version); this breaks egit 4.1.1 views when installed into Mars.2, because Mars.2 site does not include org.eclipse.egit.ui.importer 4.1.1.201511131810-r, and you confuse egit when you have both jgit 4.0 and 4.1 installed, disabling views and preferences.
> Solution proposed is to add org.eclipse.egit.ui.importer 4.1.1.201511131810-r to the composite site from which JBT 4.3.0.Final and JBDS 9.0.0.GA are installed, so that when org.eclipse.egit.ui.importer is installed, p2 can select the 4.1.1 version instead of the 4.0.0 version.
> I would want to pull a mirror of http://download.eclipse.org/egit/updates-4.1.1/ onto download.jboss.org if we're cool with this solution.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21821) JBT 4.3.0.Final / JBDS 9.0.0.GA target platforms include org.eclipse.egit.importer.ui 4.0, which installs jgit 4.0; this breaks egit 4.1.1 views when JBT 4.3.0 or JBDS 9.0.0 are installed into Mars.2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21821?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21821:
------------------------------------
Max asked: "and i'm wondering why is it that org.eclipse.egit.importer.ui 4.0.0. installs jgit 4.0 - does its version range to jgit limit it to 4.0.x ?"
{code:title=org.eclipse.egit.ui.importer_4.0.0.201506090130-r.jar/META-INF/MANIFEST.MF}
Require-Bundle: org.eclipse.ui,org.eclipse.core.runtime,org.eclipse.e4
.ui.importer;bundle-version="0.1.0",org.eclipse.jgit;bundle-version="
[4.0.0,4.1.0)"{code}
{code:title=org.eclipse.egit.ui.importer_4.1.1.201511131810-r.jar/META-INF/MANIFEST.MF}
Require-Bundle: org.eclipse.ui,org.eclipse.core.runtime,org.eclipse.e4
.ui.importer;bundle-version="0.1.0",org.eclipse.jgit;bundle-version="
[4.1.0,4.2.0)"{code}
> JBT 4.3.0.Final / JBDS 9.0.0.GA target platforms include org.eclipse.egit.importer.ui 4.0, which installs jgit 4.0; this breaks egit 4.1.1 views when JBT 4.3.0 or JBDS 9.0.0 are installed into 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
> -----
> JBT 4.3.0.Final / JBDS 9.0.0.GA target platforms include org.eclipse.egit.importer.ui 4.0.0.201506090130-r (Mars.1 version), which installs jgit 4.0.3.201509231615-r (Mars.1 version); this breaks egit 4.1.1 views when installed into Mars.2, because Mars.2 site does not include org.eclipse.egit.ui.importer 4.1.1.201511131810-r, and you confuse egit when you have both jgit 4.0 and 4.1 installed, disabling views and preferences.
> Solution proposed is to add org.eclipse.egit.ui.importer 4.1.1.201511131810-r to the composite site from which JBT 4.3.0.Final and JBDS 9.0.0.GA are installed, so that when org.eclipse.egit.ui.importer is installed, p2 can select the 4.1.1 version instead of the 4.0.0 version.
> I would want to pull a mirror of http://download.eclipse.org/egit/updates-4.1.1/ onto download.jboss.org if we're cool with this solution.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years