November 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4133) org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4133: ---------------------------------- PRs to update TPs: https://github.com/jbosstools/jbosstools-target-platforms/pull/243 https://github.com/jbosstools/jbosstools-target-platforms/pull/244 > org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer > -------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4133 > URL: https://issues.jboss.org/browse/JBDS-4133 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm, webservices > Affects Versions: 10.2.0.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: lucene3.5corevs.5.4.1analyzers-common.png, lucene3.5corevs.5.4.1queryparser.png > > > I'm getting this problem after running the HTML5 quickstart. I've installed this [1] version of the rpm. > {code} > !ENTRY org.eclipse.core.jobs 4 2 2016-10-26 16:22:07.578 > !MESSAGE An internal error occurred during: "JAX-RS Metamodel build...". > !STACK 0 > java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.<init>(JaxrsMetamodel.java:163) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.create(JaxrsMetamodel.java:278) > at org.jboss.tools.ws.jaxrs.core.metamodel.domain.JaxrsMetamodelLocator.get(JaxrsMetamodelLocator.java:120) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:68) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.lang.ClassNotFoundException: org.apache.lucene.analysis.standard.StandardAnalyzer cannot be found by org.jboss.tools.ws.jaxrs.core_1.9.2.v20161011-1002 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 5 more > {code} > [1] https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/20... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23432) Upgrade Forge Runtime to 3.3.3.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23432?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-23432. ------------------------------------- Resolution: Done > Upgrade Forge Runtime to 3.3.3.Final > ------------------------------------ > > Key: JBIDE-23432 > URL: https://issues.jboss.org/browse/JBIDE-23432 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.4.2.AM2 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.4.2.AM3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23432) Upgrade Forge Runtime to 3.3.3.Final

by George Gastaldi (JIRA)

George Gastaldi created JBIDE-23432: --------------------------------------- Summary: Upgrade Forge Runtime to 3.3.3.Final Key: JBIDE-23432 URL: https://issues.jboss.org/browse/JBIDE-23432 Project: Tools (JBoss Tools) Issue Type: Component Upgrade Components: forge Affects Versions: 4.4.2.AM2 Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 4.4.2.AM3 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4133) org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-4133: ---------------------------------- The PR I submitted was failing because of Tycho but was working in Eclipse so this maybe the same problem with Xavier's PR > org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer > -------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4133 > URL: https://issues.jboss.org/browse/JBDS-4133 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm, webservices > Affects Versions: 10.2.0.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: lucene3.5corevs.5.4.1analyzers-common.png, lucene3.5corevs.5.4.1queryparser.png > > > I'm getting this problem after running the HTML5 quickstart. I've installed this [1] version of the rpm. > {code} > !ENTRY org.eclipse.core.jobs 4 2 2016-10-26 16:22:07.578 > !MESSAGE An internal error occurred during: "JAX-RS Metamodel build...". > !STACK 0 > java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.<init>(JaxrsMetamodel.java:163) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.create(JaxrsMetamodel.java:278) > at org.jboss.tools.ws.jaxrs.core.metamodel.domain.JaxrsMetamodelLocator.get(JaxrsMetamodelLocator.java:120) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:68) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.lang.ClassNotFoundException: org.apache.lucene.analysis.standard.StandardAnalyzer cannot be found by org.jboss.tools.ws.jaxrs.core_1.9.2.v20161011-1002 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 5 more > {code} > [1] https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/20... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4140) Setting 'Path' variable does not work for child_process on OS X

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4140?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4140. ----------------------------- Apparently, Windows now only works with 'Path', with 'PATH' I'm getting the undefined and later on problems with calling vagrant. > Setting 'Path' variable does not work for child_process on OS X > --------------------------------------------------------------- > > Key: JBDS-4140 > URL: https://issues.jboss.org/browse/JBDS-4140 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM3 > Environment: Mac OS X, > Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.2.0.AM3 > > > Current code sets up environment variable using name 'Path' for running command with child_process module and it works perfectly only under windows. On OS X it it doesn't work, thats why install log has entry > {code}Setting PATH variable to 'undefined:/bin'{code}. > Under windows both names 'Path' and 'PATH' works with child_process module. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4156) Skip detected components in cdk's createEnvironment

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4156?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4156: ------------------------------ Description: When installing cdk using detected components, the locations stored to the environment are empty (""/bin to be precise). In the end it generates this log entry: {noformat}Thu, 03 Nov 2016 11:46:04 GMT-INFO: cdk - Set PATH environment variable to 'undefined;bin;bin;'{noformat} was: When installing cdk using detected components, the locations stored to the environment are empty. In the end it generates this log entry: {noformat}Thu, 03 Nov 2016 11:46:04 GMT-INFO: cdk - Set PATH environment variable to 'undefined;bin;bin;'{noformat} > Skip detected components in cdk's createEnvironment > --------------------------------------------------- > > Key: JBDS-4156 > URL: https://issues.jboss.org/browse/JBDS-4156 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.2.0.AM3 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > > When installing cdk using detected components, the locations stored to the environment are empty (""/bin to be precise). In the end it generates this log entry: > {noformat}Thu, 03 Nov 2016 11:46:04 GMT-INFO: cdk - Set PATH environment variable to 'undefined;bin;bin;'{noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4156) Skip detected components in cdk's createEnvironment

by Jan Richter (JIRA)

Jan Richter created JBDS-4156: --------------------------------- Summary: Skip detected components in cdk's createEnvironment Key: JBDS-4156 URL: https://issues.jboss.org/browse/JBDS-4156 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Enhancement Components: platform-installer Affects Versions: 10.2.0.AM3 Reporter: Jan Richter Assignee: Denis Golovin Priority: Minor When installing cdk using detected components, the locations stored to the environment are empty. In the end it generates this log entry: {noformat}Thu, 03 Nov 2016 11:46:04 GMT-INFO: cdk - Set PATH environment variable to 'undefined;bin;bin;'{noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-975) SY - Avoid waiting for the job 'Synchronizing EMF resources'

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-975?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-975. ------------------------------ PR was pushed to master > SY - Avoid waiting for the job 'Synchronizing EMF resources' > ------------------------------------------------------------ > > Key: JBTIS-975 > URL: https://issues.jboss.org/browse/JBTIS-975 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, switchyard > Affects Versions: 4.4.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.4.0.Final > > > Sometimes It happens that some jobs take more than one minute and that's why my tests fail > {code} > org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: The following jobs are still running > Refreshing SwitchYard project configuration. > Synchronizing EMF resources > Updating Maven Project > {code} > Usually the test 'SwitchYardIntegrationDroolsTest' fails due to the above exception. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-444) Remember last selected registry account used when pulling an image [EBZ#506967]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-444: --------------------------------------- Summary: Remember last selected registry account used when pulling an image [EBZ#506967] Key: ERT-444 URL: https://issues.jboss.org/browse/ERT-444 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Priority: Trivial - Open Docker Explorer - right-click on Images node - Pull... - add a registry account - pull an image from the registry account - right-click on Images node - Pull... --> the selected Registry account is https://index.docker.io , it would be convenient to preselect the latest registry account used -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23213) Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23213?page=com.atlassian.jira.plugi... ] Supriya Bharadwaj commented on JBIDE-23213: ------------------------------------------- Added a note in RHDEVDOCS-249 to look at this issue when updating the Configs page for the Banksia release. > Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23213 > URL: https://issues.jboss.org/browse/JBIDE-23213 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.4.2.AM3 > > > It's time to review the available platforms on which we test devstudio / jbt. > Specifically, we list Ubuntu 14.04 LTS and 16.04 LTS, but there will be newer versions available [0] when 10.2 / 4.4.2 is released in Dec 2016. > [0] https://wiki.ubuntu.com/Releases > * Should we move to 16.04.1 LTS and 16.10? > * Should we move to 14.04.5 LTS and 16.04.1 LTS ? > * Should we move to 14.04.5 LTS and 16.10? > Also, it was decided today in the 5x5 call that we should be supporting Fedora 23 and 24 (where currently we support 22 and 23) [1]. > [1] https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... > But Fedora 25 will be out on Nov 15 [2], which is 2 weeks before the 10.2 final code freeze on Nov 29, so we probably have time to contain & support that, right? > [2] https://fedoraproject.org/wiki/Releases/25/Schedule > * Should we move to F24 and F25? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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