June 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-27322) Cannot start Eclipse when installing from update site

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27322?page=com.atlassian.jira.plug... ] Stephane Bouchet commented on JBIDE-27322: ------------------------------------------ Workaround is to start eclipse using jdk11, exit eclipse and start again using jdk1.8... attached is the same log with this scenario : [^.log] > Cannot start Eclipse when installing from update site > ----------------------------------------------------- > > Key: JBIDE-27322 > URL: https://issues.redhat.com/browse/JBIDE-27322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.16.0.AM1 > Reporter: Stephane Bouchet > Priority: Blocker > Fix For: 4.16.0.Final > > Attachments: .log, .log > > > when smoke testing4.16.0.AM1, using a bare Eclipse 4.16 and installing everything from update site, I cannot restart eclipse. > the attached log indicates an SWT theme problem, but no JBoss stacktrace involved. > Test performed using Linux RHEL 8, with jdk1.8 > Affect both Devstudio and jbosstools. > When switching to JDK11, the problem went away. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27322) Cannot start Eclipse when installing from update site

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27322?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-27322: ------------------------------------- Attachment: .log > Cannot start Eclipse when installing from update site > ----------------------------------------------------- > > Key: JBIDE-27322 > URL: https://issues.redhat.com/browse/JBIDE-27322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.16.0.AM1 > Reporter: Stephane Bouchet > Priority: Blocker > Fix For: 4.16.0.Final > > Attachments: .log, .log > > > when smoke testing4.16.0.AM1, using a bare Eclipse 4.16 and installing everything from update site, I cannot restart eclipse. > the attached log indicates an SWT theme problem, but no JBoss stacktrace involved. > Test performed using Linux RHEL 8, with jdk1.8 > Affect both Devstudio and jbosstools. > When switching to JDK11, the problem went away. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27322) Cannot start Eclipse when installing from update site

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27322?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-27322: ------------------------------------- Fix Version/s: 4.16.0.Final > Cannot start Eclipse when installing from update site > ----------------------------------------------------- > > Key: JBIDE-27322 > URL: https://issues.redhat.com/browse/JBIDE-27322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.16.0.AM1 > Reporter: Stephane Bouchet > Priority: Blocker > Fix For: 4.16.0.Final > > Attachments: .log > > > when smoke testing4.16.0.AM1, using a bare Eclipse 4.16 and installing everything from update site, I cannot restart eclipse. > the attached log indicates an SWT theme problem, but no JBoss stacktrace involved. > Test performed using Linux RHEL 8, with jdk1.8 > Affect both Devstudio and jbosstools. > When switching to JDK11, the problem went away. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27322) Cannot start Eclipse when installing from update site

by Stephane Bouchet (Jira)

Stephane Bouchet created JBIDE-27322: ---------------------------------------- Summary: Cannot start Eclipse when installing from update site Key: JBIDE-27322 URL: https://issues.redhat.com/browse/JBIDE-27322 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.16.0.AM1 Reporter: Stephane Bouchet Attachments: .log when smoke testing4.16.0.AM1, using a bare Eclipse 4.16 and installing everything from update site, I cannot restart eclipse. the attached log indicates an SWT theme problem, but no JBoss stacktrace involved. Test performed using Linux RHEL 8, with jdk1.8 Affect both Devstudio and jbosstools. When switching to JDK11, the problem went away. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27320) Remove old jbosstools.test.jre vars from parent POM

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-27320?page=com.atlassian.jira.plug... ] Josef Kopriva commented on JBIDE-27320: --------------------------------------- [~jeffmaury] yes, It was used for testing old runtimes, I am really not sure if we need this properties anymore. I was referring at this note: https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... Maybe it will be needed by some unit tests. I want to investigate it, if it is still necessary or not. > Remove old jbosstools.test.jre vars from parent POM > --------------------------------------------------- > > Key: JBIDE-27320 > URL: https://issues.redhat.com/browse/JBIDE-27320 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, integration-tests, qa, server > Affects Versions: 4.16.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.16.0.Final > > > In parent POM are still variables for old JDKs: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > like 5, 6 and 7. > We do not support these JDKs anymore, so its an artifact. > Unfortunately these variables are also defined in some ITests(server, fuse...). It needs to be carefully removed and all ITests must be checked, if it is ok. > These variables are also defined on Jenkins(dev-platform and PSI), so it needs to be removed there too. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27320) Remove old jbosstools.test.jre vars from parent POM

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27320?page=com.atlassian.jira.plug... ] Jeff MAURY commented on JBIDE-27320: ------------------------------------ I think they are required by old versions of JBoss/EAP. > Remove old jbosstools.test.jre vars from parent POM > --------------------------------------------------- > > Key: JBIDE-27320 > URL: https://issues.redhat.com/browse/JBIDE-27320 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, integration-tests, qa, server > Affects Versions: 4.16.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.16.0.Final > > > In parent POM are still variables for old JDKs: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > like 5, 6 and 7. > We do not support these JDKs anymore, so its an artifact. > Unfortunately these variables are also defined in some ITests(server, fuse...). It needs to be carefully removed and all ITests must be checked, if it is ok. > These variables are also defined on Jenkins(dev-platform and PSI), so it needs to be removed there too. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27321) Add WF20 in jboss-stacks

by Josef Kopriva (Jira)

Josef Kopriva created JBIDE-27321: ------------------------------------- Summary: Add WF20 in jboss-stacks Key: JBIDE-27321 URL: https://issues.redhat.com/browse/JBIDE-27321 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.16.0.AM1 Reporter: Josef Kopriva Assignee: Josef Kopriva Fix For: 4.16.0.AM1 Server adapter for WF cannot be created. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27320) Remove old jbosstools.test.jre vars from parent POM

by Josef Kopriva (Jira)

Josef Kopriva created JBIDE-27320: ------------------------------------- Summary: Remove old jbosstools.test.jre vars from parent POM Key: JBIDE-27320 URL: https://issues.redhat.com/browse/JBIDE-27320 Project: Tools (JBoss Tools) Issue Type: Task Components: build, integration-tests, qa, server Affects Versions: 4.16.0.AM1 Reporter: Josef Kopriva Assignee: Josef Kopriva Fix For: 4.16.0.Final In parent POM are still variables for old JDKs: https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... like 5, 6 and 7. We do not support these JDKs anymore, so its an artifact. Unfortunately these variables are also defined in some ITests(server, fuse...). It needs to be carefully removed and all ITests must be checked, if it is ok. These variables are also defined on Jenkins(dev-platform and PSI), so it needs to be removed there too. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27319) Review/Update server ITests for WF20

by Josef Kopriva (Jira)

Josef Kopriva created JBIDE-27319: ------------------------------------- Summary: Review/Update server ITests for WF20 Key: JBIDE-27319 URL: https://issues.redhat.com/browse/JBIDE-27319 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests, server Affects Versions: 4.16.0.AM1 Reporter: Josef Kopriva Assignee: Josef Kopriva Fix For: 4.16.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27284) OpenShift ODO View: wrong label in Create component wizard

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-27284?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-27284. --------------------------------- Closing, this is fixed now. Verified in: Red Hat CodeReady Studio Version: 12.16.0.AM1 Build id: AM1-v20200618-0115-B6507 Build date: 20200618-0115 > OpenShift ODO View: wrong label in Create component wizard > ---------------------------------------------------------- > > Key: JBIDE-27284 > URL: https://issues.redhat.com/browse/JBIDE-27284 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.16.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Minor > Fix For: 4.16.0.AM1 > > Attachments: image-2020-05-21-12-06-17-521.png > > > !image-2020-05-21-12-06-17-521.png|thumbnail! > There should be something else like: "Create component" or "Component details" or "Component parameters" -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 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 2020