December 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25455) JBoss Tools marketplace listing includes org.eclipse features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25455?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-25455 at 12/12/17 10:47 AM: --------------------------------------------------------------- Here's the list of org.eclipse feature currently in the jbosstools markeplace entry [1]. !jbosstools-eclipse-plugins-marketplace.png|thumbnail! [1] https://marketplace.eclipse.org/content/jboss-tools/edit I would imagine we should remove all of them? Or maybe keep buildship, since for some reason it's included in the JBT update site [2], [3]? [2] http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4.... [3] http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4.... was (Author: nickboldt): Here's the list of org.eclipse feature currently in the jbosstools markeplace entry [1]. !jbosstools-eclipse-plugins-marketplace.png|thumbnail! [1] https://marketplace.eclipse.org/content/jboss-tools/edit I would imagine we should remove all of them? Or maybe keep buildship, since for some reason it's included in the JBT update site? > JBoss Tools marketplace listing includes org.eclipse features > ------------------------------------------------------------- > > Key: JBIDE-25455 > URL: https://issues.jboss.org/browse/JBIDE-25455 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.2.Final > > Attachments: jbosstools-eclipse-plugins-marketplace.png > > > Someone added org.eclipse.buildship and org.eclipse.wst.* features to the Marketplace listing as optional-selected features. > Shouldn't these be installed via requirements from JBT features, and therefore not needed on the site? > The list of sanctioned features in the CoreTools category on the JBT site is here: > http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4.... > So... why did the other features get added? And if they SHOULD be there, they should also be added to the JBT site too, for consistency. Right? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25455) JBoss Tools marketplace listing includes org.eclipse features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25455?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25455: ------------------------------------ Here's the list of org.eclipse plugins currently in the jbosstools markeplace entry [1]. !jbosstools-eclipse-plugins-marketplace.png|thumbnail! [1] https://marketplace.eclipse.org/content/jboss-tools/edit > JBoss Tools marketplace listing includes org.eclipse features > ------------------------------------------------------------- > > Key: JBIDE-25455 > URL: https://issues.jboss.org/browse/JBIDE-25455 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.2.Final > > Attachments: jbosstools-eclipse-plugins-marketplace.png > > > Someone added org.eclipse.buildship and org.eclipse.wst.* features to the Marketplace listing as optional-selected features. > Shouldn't these be installed via requirements from JBT features, and therefore not needed on the site? > The list of sanctioned features in the CoreTools category on the JBT site is here: > http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4.... > So... why did the other features get added? And if they SHOULD be there, they should also be added to the JBT site too, for consistency. Right? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25455) JBoss Tools marketplace listing includes org.eclipse features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25455?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-25455 at 12/12/17 10:47 AM: --------------------------------------------------------------- Here's the list of org.eclipse feature currently in the jbosstools markeplace entry [1]. !jbosstools-eclipse-plugins-marketplace.png|thumbnail! [1] https://marketplace.eclipse.org/content/jboss-tools/edit I would imagine we should remove all of them? Or maybe keep buildship, since for some reason it's included in the JBT update site? was (Author: nickboldt): Here's the list of org.eclipse plugins currently in the jbosstools markeplace entry [1]. !jbosstools-eclipse-plugins-marketplace.png|thumbnail! [1] https://marketplace.eclipse.org/content/jboss-tools/edit > JBoss Tools marketplace listing includes org.eclipse features > ------------------------------------------------------------- > > Key: JBIDE-25455 > URL: https://issues.jboss.org/browse/JBIDE-25455 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.2.Final > > Attachments: jbosstools-eclipse-plugins-marketplace.png > > > Someone added org.eclipse.buildship and org.eclipse.wst.* features to the Marketplace listing as optional-selected features. > Shouldn't these be installed via requirements from JBT features, and therefore not needed on the site? > The list of sanctioned features in the CoreTools category on the JBT site is here: > http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4.... > So... why did the other features get added? And if they SHOULD be there, they should also be added to the JBT site too, for consistency. Right? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25455) JBoss Tools marketplace listing includes org.eclipse features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25455?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25455: ------------------------------- Attachment: jbosstools-eclipse-plugins-marketplace.png > JBoss Tools marketplace listing includes org.eclipse features > ------------------------------------------------------------- > > Key: JBIDE-25455 > URL: https://issues.jboss.org/browse/JBIDE-25455 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.2.Final > > Attachments: jbosstools-eclipse-plugins-marketplace.png > > > Someone added org.eclipse.buildship and org.eclipse.wst.* features to the Marketplace listing as optional-selected features. > Shouldn't these be installed via requirements from JBT features, and therefore not needed on the site? > The list of sanctioned features in the CoreTools category on the JBT site is here: > http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4.... > So... why did the other features get added? And if they SHOULD be there, they should also be added to the JBT site too, for consistency. Right? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25441) Problems with CDI Builder and scanning Jars which support Java 9

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25441?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25441: ------------------------------- Sprint: devex #142 December 2017 > Problems with CDI Builder and scanning Jars which support Java 9 > ---------------------------------------------------------------- > > Key: JBIDE-25441 > URL: https://issues.jboss.org/browse/JBIDE-25441 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, common > Affects Versions: 4.5.1.Final, 4.5.2.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.x > > > As reported in https://developer.jboss.org/message/978446?et=watches.email.thread#978446: > {quote} > Setup: > * Eclipse Oxygen 4.7.1 > * JBoss Tools 4.5.1.Final (also tested with latest development version 4.5.2.AM1) > * An maven web application with certain dependencies > ** So far, we found two dependencies, which lead to this jandex scaning error after upgrading to latest version > ** org.apache.logging.log4j version 2.10.0 > ** org.ow2.asm version 6.0 > > This leads to an CDI Builder IllegalStateException - see exception trace below. > Both dependencies started support for Java 9, which seems to cause this exception. > > *Apache Log4j 2.10.0 released*: http://mail-archives.apache.org/mod_mbox/www-announce/201711.mbox/%3Cdf95... > > {code} > !MESSAGE Errors running builder 'CDI (Contexts and Dependency Injection) Builder' on project 'Webapp'. > !STACK 0 > java.lang.IllegalStateException: Unknown tag! pos=4 poolCount = 24 > at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:665) > at org.jboss.jandex.Indexer.index(Indexer.java:699) > at org.jboss.tools.common.core.jandex.JandexUtil.createJarIndex(JandexUtil.java:56) > at org.jboss.tools.common.core.jandex.JandexUtil.hasAnnotation(JandexUtil.java:104) > at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.hasAnnotatedBeans(BeanArchiveDetector.java:276) > at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.resolve(BeanArchiveDetector.java:203) > at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.detectBeanModule(ClassPathMonitor.java:150) > at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:106) > at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25441) Problems with CDI Builder and scanning Jars which support Java 9

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25441?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25441: ------------------------------- Story Points: 10 > Problems with CDI Builder and scanning Jars which support Java 9 > ---------------------------------------------------------------- > > Key: JBIDE-25441 > URL: https://issues.jboss.org/browse/JBIDE-25441 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, common > Affects Versions: 4.5.1.Final, 4.5.2.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.x > > > As reported in https://developer.jboss.org/message/978446?et=watches.email.thread#978446: > {quote} > Setup: > * Eclipse Oxygen 4.7.1 > * JBoss Tools 4.5.1.Final (also tested with latest development version 4.5.2.AM1) > * An maven web application with certain dependencies > ** So far, we found two dependencies, which lead to this jandex scaning error after upgrading to latest version > ** org.apache.logging.log4j version 2.10.0 > ** org.ow2.asm version 6.0 > > This leads to an CDI Builder IllegalStateException - see exception trace below. > Both dependencies started support for Java 9, which seems to cause this exception. > > *Apache Log4j 2.10.0 released*: http://mail-archives.apache.org/mod_mbox/www-announce/201711.mbox/%3Cdf95... > > {code} > !MESSAGE Errors running builder 'CDI (Contexts and Dependency Injection) Builder' on project 'Webapp'. > !STACK 0 > java.lang.IllegalStateException: Unknown tag! pos=4 poolCount = 24 > at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:665) > at org.jboss.jandex.Indexer.index(Indexer.java:699) > at org.jboss.tools.common.core.jandex.JandexUtil.createJarIndex(JandexUtil.java:56) > at org.jboss.tools.common.core.jandex.JandexUtil.hasAnnotation(JandexUtil.java:104) > at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.hasAnnotatedBeans(BeanArchiveDetector.java:276) > at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.resolve(BeanArchiveDetector.java:203) > at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.detectBeanModule(ClassPathMonitor.java:150) > at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:106) > at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18654) run jdeps on our jars to see how dependent we are on api that might go away in Java 9

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18654?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-18654: ------------------------------------ Run against openshift, base, server, webservices and javaee without any build failures > run jdeps on our jars to see how dependent we are on api that might go away in Java 9 > ------------------------------------------------------------------------------------- > > Key: JBIDE-18654 > URL: https://issues.jboss.org/browse/JBIDE-18654 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Jeff MAURY > Fix For: 4.3.x, 4.5.2.Final > > > Java 9 JDK team have been pinging various teams to check if they got depedency on API that is scheduled to disappear in Java 9. > There is a tool called jdeps that we can use to check for this using the -jdkinternals flag. > https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool > The sooner the better we get this done as it is feedback to the Java 9 team. > If we can we should try run it on *all* jars, even eclipse ones to see what will be affected - but first of all jboss tools plugins. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1191) Support java 1.8 in tests

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1191?page=com.atlassian.jira.plugin... ] Matej Kralik closed JBTIS-1191. ------------------------------- > Support java 1.8 in tests > ------------------------- > > Key: JBTIS-1191 > URL: https://issues.jboss.org/browse/JBTIS-1191 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: QE > Affects Versions: 11.1.0.Beta1b > Reporter: Matej Kralik > Assignee: Matej Kralik > Fix For: 11.1.0.Beta1b > > > Support java 1.8 features in tests. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1192) Create test for connection view

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1192?page=com.atlassian.jira.plugin... ] Matej Kralik closed JBTIS-1192. ------------------------------- > Create test for connection view > ------------------------------- > > Key: JBTIS-1192 > URL: https://issues.jboss.org/browse/JBTIS-1192 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, teiid > Affects Versions: 11.1.0.Beta1b > Reporter: Matej Kralik > Assignee: Matej Kralik > Fix For: 11.1.0.Beta1b > > > Create test which will be test new Connection view -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25456) Kubernetes editor: create editor and integration for yaml-language-server

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-25456: ---------------------------------------- Summary: Kubernetes editor: create editor and integration for yaml-language-server Key: JBIDE-25456 URL: https://issues.jboss.org/browse/JBIDE-25456 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.5.1.AM2 Reporter: Andre Dietisheim Given that there's a need to edit kubernetes/openshift json/yaml such an editor would be very helpful. We could easily create that by creating an editor that's based on lsp4e and integrating the yaml-language-server. * The yaml-langauge server: https://github.com/redhat-developer/yaml-language-server * Similar integration that's already been done for fabric8 analytics: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 December 2017