June 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26074) OpenShift explorer: project is not listed for open.paas.redhat.com

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26074?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26074: ------------------------------------- Labels: connection explorer (was: ) > OpenShift explorer: project is not listed for open.paas.redhat.com > ------------------------------------------------------------------ > > Key: JBIDE-26074 > URL: https://issues.jboss.org/browse/JBIDE-26074 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM2 > Reporter: Andre Dietisheim > Labels: connection, project > Fix For: 4.6.x > > Attachments: image-2018-06-01-16-33-47-300.png, image-2018-06-01-16-37-32-447.png > > > steps: > # ASSERT: have at least 1 connection to https://open.paas.redhat.com > # ASSERT: have at least 1 project in your OpenShift > # EXEC: in OpenShift Explorer: unfold connection > Result: > You're project is not listed > !image-2018-06-01-16-33-47-300.png! > while it is in the "Manage Projects" wizard: > !image-2018-06-01-16-37-32-447.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26074) OpenShift explorer: project is not listed for open.paas.redhat.com

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26074?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26074: ------------------------------------- Labels: connection project (was: connection explorer) > OpenShift explorer: project is not listed for open.paas.redhat.com > ------------------------------------------------------------------ > > Key: JBIDE-26074 > URL: https://issues.jboss.org/browse/JBIDE-26074 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM2 > Reporter: Andre Dietisheim > Labels: connection, project > Fix For: 4.6.x > > Attachments: image-2018-06-01-16-33-47-300.png, image-2018-06-01-16-37-32-447.png > > > steps: > # ASSERT: have at least 1 connection to https://open.paas.redhat.com > # ASSERT: have at least 1 project in your OpenShift > # EXEC: in OpenShift Explorer: unfold connection > Result: > You're project is not listed > !image-2018-06-01-16-33-47-300.png! > while it is in the "Manage Projects" wizard: > !image-2018-06-01-16-37-32-447.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26074) OpenShift explorer: project is not listed for open.paas.redhat.com

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26074?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-26074: ------------------------------------------ Weird enough, a few hours later, I cannot reproduce this. And I never could reproduce this with api.engint.openshift.com, > OpenShift explorer: project is not listed for open.paas.redhat.com > ------------------------------------------------------------------ > > Key: JBIDE-26074 > URL: https://issues.jboss.org/browse/JBIDE-26074 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM2 > Reporter: Andre Dietisheim > Fix For: 4.6.x > > Attachments: image-2018-06-01-16-33-47-300.png, image-2018-06-01-16-37-32-447.png > > > steps: > # ASSERT: have at least 1 connection to https://open.paas.redhat.com > # ASSERT: have at least 1 project in your OpenShift > # EXEC: in OpenShift Explorer: unfold connection > Result: > You're project is not listed > !image-2018-06-01-16-33-47-300.png! > while it is in the "Manage Projects" wizard: > !image-2018-06-01-16-37-32-447.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26074) OpenShift explorer: project is not listed for open.paas.redhat.com

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26074?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26074: ------------------------------------- Fix Version/s: 4.6.x > OpenShift explorer: project is not listed for open.paas.redhat.com > ------------------------------------------------------------------ > > Key: JBIDE-26074 > URL: https://issues.jboss.org/browse/JBIDE-26074 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM2 > Reporter: Andre Dietisheim > Fix For: 4.6.x > > Attachments: image-2018-06-01-16-33-47-300.png, image-2018-06-01-16-37-32-447.png > > > steps: > # ASSERT: have at least 1 connection to https://open.paas.redhat.com > # ASSERT: have at least 1 project in your OpenShift > # EXEC: in OpenShift Explorer: unfold connection > Result: > You're project is not listed > !image-2018-06-01-16-33-47-300.png! > while it is in the "Manage Projects" wizard: > !image-2018-06-01-16-37-32-447.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26075) Support FacesContext Injection

by Cody Lerum (JIRA)

Cody Lerum created JBIDE-26075: ---------------------------------- Summary: Support FacesContext Injection Key: JBIDE-26075 URL: https://issues.jboss.org/browse/JBIDE-26075 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi, jsf Affects Versions: 4.5.3.Final Environment: JSF 2.3 Reporter: Cody Lerum JSF 2.3 now produces various beans for CDI https://arjan-tijms.omnifaces.org/p/jsf-23.html#1316 However currently the following gives a No bean is eligible for injection to the injection point [JSR-365 §5.2.2] {code} @Inject private FacesContext facesContext; {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4708) Remediation prevents installation of devstudio 12 AND egit 5.0 concurrently

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4708?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4708: ----------------------------- Sprint: devex #150 June 2018 > Remediation prevents installation of devstudio 12 AND egit 5.0 concurrently > --------------------------------------------------------------------------- > > Key: JBDS-4708 > URL: https://issues.jboss.org/browse/JBDS-4708 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 12.0.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 12.0.0.AM3 > > Attachments: remediation-1.png, remediation-2.png, remediation-jbt-central.png > > > Problem appears to be a hard upper limit from org.sonatype.m2e.egit 0.15.0.20161027 on egit.core [3.0.0,5.0.0). > {code} > Cannot complete the install because of a conflicting dependency. > Software being installed: Red Hat JBoss Developer Studio (Core Features) 12.0.0.v20180525-1013 (com.jboss.devstudio.core.feature.feature.group 12.0.0.v20180525-1013) > Software currently installed: Git integration for Eclipse 5.0.0.201805151920-m7 (org.eclipse.egit.feature.group 5.0.0.201805151920-m7) > Only one of the following can be installed at once: > Git integration for Eclipse - Core 4.11.0.201803080745-r (org.eclipse.egit.core 4.11.0.201803080745-r) > Git integration for Eclipse - Core 5.0.0.201805151920-m7 (org.eclipse.egit.core 5.0.0.201805151920-m7) > Git integration for Eclipse - Core 4.10.0.201712302008-r (org.eclipse.egit.core 4.10.0.201712302008-r) > Git integration for Eclipse - Core 5.0.0.201805221745-rc1 (org.eclipse.egit.core 5.0.0.201805221745-rc1) > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (Core Features) 12.0.0.v20180525-1013 (com.jboss.devstudio.core.feature.feature.group 12.0.0.v20180525-1013) > To: org.eclipse.equinox.p2.iu; com.jboss.devstudio.core.rpmdeps.feature.feature.group [12.0.0.v20180418-2342,12.0.0.v20180418-2342] > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (Feature Dependencies) 12.0.0.v20180418-2342 (com.jboss.devstudio.core.rpmdeps.feature.feature.group 12.0.0.v20180418-2342) > To: org.eclipse.equinox.p2.iu; org.sonatype.m2e.egit.feature.feature.group 0.0.0 > Cannot satisfy dependency: > From: Git integration for Eclipse 5.0.0.201805151920-m7 (org.eclipse.egit.feature.group 5.0.0.201805151920-m7) > To: org.eclipse.equinox.p2.iu; org.eclipse.egit.core [5.0.0.201805151920-m7,5.0.0.201805151920-m7] > Cannot satisfy dependency: > From: Maven SCM Handler for EGit 0.15.0.201610271523 (org.sonatype.m2e.egit 0.15.0.201610271523) > To: osgi.bundle; org.eclipse.egit.core [3.0.0,5.0.0) > Cannot satisfy dependency: > From: Maven SCM Handler for EGit 0.15.0.201610271523 (org.sonatype.m2e.egit.feature.feature.group 0.15.0.201610271523) > To: org.eclipse.equinox.p2.iu; org.sonatype.m2e.egit [0.15.0.201610271523,0.15.0.201610271523]{code} > As such we can either: > * install devstudio (which requires m2e.egit) and uninstall egit and egit.mylyn features to do so, or > !remediation-2.png|thumbnail! > * upgrade to egit 5.0.0.20180522 (rc1) and not be able to install devstudio 12.0.0.AM2. > !remediation-1.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26038) [Red Hat Central] Update to latest Subclipse

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26038?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26038: ------------------------------- Sprint: devex #150 June 2018 > [Red Hat Central] Update to latest Subclipse > -------------------------------------------- > > Key: JBIDE-26038 > URL: https://issues.jboss.org/browse/JBIDE-26038 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.5.3.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.6.0.AM3 > > > An error has been reported on the sme-jbds mail ling list: > http://post-office.corp.redhat.com/archives/sme-jbds/2018-May/msg00004.html > {noformat} > Hi, > I have a customer who is having issues with Subversion in JBDS 11.3. > They have installed Subclipse + SVNKit from RedHat Central and then create a new project, then add the project to SVN. They then update a dummy text file in the project. > They then try to synchronize the project and after this all of the team options are greyed out. > The only exception in the log is: > !ENTRY org.tigris.subversion.subclipse.core 4 -6 2018-05-10 15:41:57.217 > !MESSAGE The SVN synchronization information for 'jClaretyBatchClientProject' has become corrupt or does not exist. > !ENTRY org.tigris.subversion.subclipse.ui 4 -6 2018-05-10 15:41:57.217 > !MESSAGE Property Exception > !STACK 0 > java.lang.NullPointerException > at org.tigris.subversion.subclipse.ui.properties.SVNPropertyPage.getStatus(SVNPropertyPage.java:290) > at org.tigris.subversion.subclipse.ui.properties.SVNPropertyPage.createContents(SVNPropertyPage.java:81) > at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:241) > at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1426) > at org.eclipse.jface.preference.PreferenceDialog$8.run(PreferenceDialog.java:1193) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44) > ... > If they download the latest Subclipse version plus JavaHL and use this instead of SVNKit it works. > They wanted to have JavaHL as an option in RedHat Central but I advised this wasn't going to happen as per [1]. > They raised the issue with Subclipse with this response: > "There are no options in the product that are predicated on using one adapter or the other. There can be bugs or slight differences in behavior in one API implementation or the other, but both provide all of the API's we use. JavaHL is already the default implementation provided that it has been installed and is available. > So obviously you had some kind of problem here, but your diagnosis of the causes was not correct. I do generally recommend you use JavaHL if possible, since that is the API implementation that comes from Subversion itself so is going to be most compatible with the SVN command line and other clients you might be using. That said, SVNKit generally offers very good compatibility as well. > I am closing this just because I do not see that there is anything here that can be acted upon." > Any ideas on why SVNKit might not be working here? > Cheers > Dave > [1] https://issues.jboss.org/browse/JBIDE-14795 > SF case ref: https://gss--c.na7.visual.force.com/apex/Case_View?id=500A000000aqrrSIAQ > Portal Case Ref: https://access.redhat.com/support/cases/#/case/02094880 > {noformat} > I tried and was able to reproduce. > I then tried but installed from https://dl.bintray.com/subclipse/releases/subclipse/4.2.x instead of Red Hat Central and the error is gone > So I compared both update sites (https://devstudio.redhat.com/11/stable/updates/ and https://dl.bintray.com/subclipse/releases/subclipse/4.2.x) and noticed that org.tmatesoft.svnkit is 1.8.15 in DevStudio and 1.8.12 in Subclipse -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4706) Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4706?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4706: ----------------------------- Sprint: devex #150 June 2018 > Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text > --------------------------------------------------------------------------------------------- > > Key: JBDS-4706 > URL: https://issues.jboss.org/browse/JBDS-4706 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Affects Versions: 12.0.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 12.0.0.AM3 > > > Branding has requested that we rename devstudio from "Red Hat JBoss Developer Studio" to "Red Hat Developer Studio". > We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25597: ------------------------------- Sprint: devex #148 April 2018, devex #150 June 2018 (was: devex #148 April 2018) > TP: create target platforms based on Eclipse Photon > --------------------------------------------------- > > Key: JBIDE-25597 > URL: https://issues.jboss.org/browse/JBIDE-25597 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: target-platform > Fix For: 4.6.0.AM3, 4.6.0.Final > > Attachments: base.log > > > In order to start Photon based builds, we need a working Photon based target platform > For sprint 148 / AM1: Photon.0.M6 > For sprint 149 / AM2: Photon.0.M7 > For sprint 150 / AM3: Photon.0.RC3 > For sprint 151 / GA: Photon.0.GA -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25553) Cannot create Hibernate Console Configuration for projects with java 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25553?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25553: ------------------------------------ Logs are here: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Here's the console log for the orm.test: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Looks like about 48 individual occurrences of: {code}org.hibernate.DuplicateMappingException: Duplicate query mapping userSessionData{code} So... would that cause a timeout? > Cannot create Hibernate Console Configuration for projects with java 9 > ---------------------------------------------------------------------- > > Key: JBIDE-25553 > URL: https://issues.jboss.org/browse/JBIDE-25553 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.5.2.AM2 > Reporter: Rastislav Wagner > Assignee: Koen Aers > Priority: Critical > Fix For: 4.6.0.AM3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 2018