[JBoss JIRA] (JBIDE-25441) Problems with CDI Builder and scanning Jars which support Java 9
by Giovanni Lovato (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25441?page=com.atlassian.jira.plugi... ]
Giovanni Lovato commented on JBIDE-25441:
-----------------------------------------
I'm using this update site: https://tools.jboss.org/downloads/jbosstools/oxygen/4.5.x.Nightly.html
But I also see the PR of this issue is still open and not yet merged, maybe it's that the cause?
> 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.2.AM3
>
>
> 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
[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 commented on JBIDE-25441:
------------------------------------
[~heruan] what's your plugin version ?
> 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.2.AM3
>
>
> 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
[JBoss JIRA] (JBIDE-25441) Problems with CDI Builder and scanning Jars which support Java 9
by Giovanni Lovato (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25441?page=com.atlassian.jira.plugi... ]
Giovanni Lovato commented on JBIDE-25441:
-----------------------------------------
I'm still experiencing this, also with latest snapshots. Should this be reopened?
> 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.2.AM3
>
>
> 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
[JBoss JIRA] (JBDS-4640) Typo in JBoss Developer Studio Installation screen
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4640?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4640:
--------------------------------
Story Points: 1
Sprint: devex #143 January 2018
> Typo in JBoss Developer Studio Installation screen
> --------------------------------------------------
>
> Key: JBDS-4640
> URL: https://issues.jboss.org/browse/JBDS-4640
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 11.1.0.GA, 11.2.0.AM2
> Reporter: Melissa Flinn
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 11.2.0.GA
>
> Attachments: DevStudioInstallScreen_wTypo.png
>
>
> I noticed this issue in a previous GA release and in the latest release from Dec 22 that I just installed on my Lenovo laptop
> Red Hat JBoss Developer Studio
> Version: 11.2.0.AM3
> Build id: AM3-v20171222-0707-B1813
> Build date: 20171222-0707
> In the Dev Studio Installer - Step 1 of 10 - there is a typo:
> Click the "Next" Button to proceed*ed* to the next screen.
> "proceeded" should be "proceed" as in:
> Click the "Next" Button to proceed to the next screen.
> Attached is a screen shot.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBDS-4640) Typo in JBoss Developer Studio Installation screen
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4640?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-4640:
-----------------------------------
Assignee: Denis Golovin
> Typo in JBoss Developer Studio Installation screen
> --------------------------------------------------
>
> Key: JBDS-4640
> URL: https://issues.jboss.org/browse/JBDS-4640
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 11.1.0.GA, 11.2.0.AM2
> Reporter: Melissa Flinn
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 11.2.0.GA
>
> Attachments: DevStudioInstallScreen_wTypo.png
>
>
> I noticed this issue in a previous GA release and in the latest release from Dec 22 that I just installed on my Lenovo laptop
> Red Hat JBoss Developer Studio
> Version: 11.2.0.AM3
> Build id: AM3-v20171222-0707-B1813
> Build date: 20171222-0707
> In the Dev Studio Installer - Step 1 of 10 - there is a typo:
> Click the "Next" Button to proceed*ed* to the next screen.
> "proceeded" should be "proceed" as in:
> Click the "Next" Button to proceed to the next screen.
> Attached is a screen shot.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBDS-4640) Typo in JBoss Developer Studio Installation screen
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4640?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4640:
--------------------------------
Fix Version/s: 11.2.0.GA
> Typo in JBoss Developer Studio Installation screen
> --------------------------------------------------
>
> Key: JBDS-4640
> URL: https://issues.jboss.org/browse/JBDS-4640
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 11.1.0.GA, 11.2.0.AM2
> Reporter: Melissa Flinn
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 11.2.0.GA
>
> Attachments: DevStudioInstallScreen_wTypo.png
>
>
> I noticed this issue in a previous GA release and in the latest release from Dec 22 that I just installed on my Lenovo laptop
> Red Hat JBoss Developer Studio
> Version: 11.2.0.AM3
> Build id: AM3-v20171222-0707-B1813
> Build date: 20171222-0707
> In the Dev Studio Installer - Step 1 of 10 - there is a typo:
> Click the "Next" Button to proceed*ed* to the next screen.
> "proceeded" should be "proceed" as in:
> Click the "Next" Button to proceed to the next screen.
> Attached is a screen shot.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months