[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 Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ]
Xavier Coulon commented on JBDS-4133:
-------------------------------------
So I have a pull request (https://github.com/jbosstools/jbosstools-webservices/pull/257) that works with Lucene 5.4.1. Besides changing the MANIFEST.MF to inport the required packages, there were also a few code changes required as part of the migration from Lucene 3.5. to 5.x. All tests pass in Eclipse with PDE when the target platform that I import has the following additions:
{code}
<!-- JBDS-4133 - Lucene 5 -->
<location includeAllPlatforms="false" includeMode="slicer" includeSource="true" type="InstallableUnit">
<repository location="http://download.jboss.org/jbosstools/updates/requirements/lucene/rh-java-..."/>
<unit id="org.apache.lucene.analyzers-common" version="5.4.1"/>
<unit id="org.apache.lucene.analyzers-smartcn" version="5.4.1"/>
<unit id="org.apache.lucene.core" version="5.4.1"/>
<unit id="org.apache.lucene.queries" version="5.4.1"/>
<unit id="org.apache.lucene.queryparser" version="5.4.1"/>
<unit id="org.apache.lucene.sandbox" version="5.4.1"/>
</location>
{code}
but I could not test it with Maven since the target platform that is downloaded does not contain the Lucene 5.4.1 bundles.
[~nickboldt], [~akazakov], please let me know if including Lucene 5.4.1 in our TP is an option that can be considered or if I should try with Lucene 5.2 instead.
> 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
[JBoss JIRA] (JBIDE-23357) Deploy Docker Wizard: Image is not revalidated if going back to Deploy an Image wizard page
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23357?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-23357:
----------------------------------------
Assignee: Viacheslav Kabanovich
Resolution: Done
merged into master
> Deploy Docker Wizard: Image is not revalidated if going back to Deploy an Image wizard page
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-23357
> URL: https://issues.jboss.org/browse/JBIDE-23357
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM3
>
>
> When I fill in valid image into the wizard and hit next, there is a check on existence of such image and its metadata are fetched. Problem is when I go back to the Deploy an Image wizard page and put there invalid image name. Finish button is still enabled and it allows user to use non-existing (made-up) image to deploy. It results in wrong deployment.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23357) Deploy Docker Wizard: Image is not revalidated if going back to Deploy an Image wizard page
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23357?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23357:
-------------------------------------
Steps to Reproduce:
ASSERT: Have a docker connection and OpenShift connection with a project.
EXEC: in OpenSHift Explorer: Select the project and select context menu item Deploy Docker Image...
ASSERT: Deploy Docker Image wizard shows up
EXEC: In wizard select the docker connection and fill in valid image name, e.g. openshift/hello-openshift.
ASSERT: Finish button is disabled.
EXEC: Click Next button.
ASSERT: Image is validated and next wizard page is shown, Finish button is enabled.
EXEC: Click back button.
ASSERT: You are on Deploy an Image wizard page and Finish is still enabled.
EXEC: Type non-existing image name (e.g. nonexisting/imagenamewtf).
RESULT: Finish button is still enabled (click on it created not working deployment)
EXPECTED RESULT: Finish button gets disabled, need to be hit Next to get to next wizard page to check image existence etc.
was:
ASSERT: Have a docker connection and OpenShift connection with a project.
EXEC: Select the project and select context menu item Deploy Docker Image...
EXEC: In wizard select the docker connection and fill in valid image name, e.g. openshift/hello-openshift.
ASSERT: Finish button is disabled.
EXEC: Click Next button.
ASSERT: Image is validated and next wizard page is shown, Finish button is enabled.
EXEC: Click back button.
ASSERT: You are on Deploy an Image wizard page and Finish is still enabled.
EXEC: Type non-existing image name (e.g. nonexisting/imagenamewtf).
RESULT: Finish button is still enabled (click on it created not working deployment)
EXPECTED RESULT: Finish button gets disabled, need to be hit Next to get to next wizard page to check image existence etc.
> Deploy Docker Wizard: Image is not revalidated if going back to Deploy an Image wizard page
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-23357
> URL: https://issues.jboss.org/browse/JBIDE-23357
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM3
>
>
> When I fill in valid image into the wizard and hit next, there is a check on existence of such image and its metadata are fetched. Problem is when I go back to the Deploy an Image wizard page and put there invalid image name. Finish button is still enabled and it allows user to use non-existing (made-up) image to deploy. It results in wrong deployment.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4139) Undefined reference in install log
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4139?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4139.
-----------------------------
Verified in B208.
> Undefined reference in install log
> ----------------------------------
>
> Key: JBDS-4139
> URL: https://issues.jboss.org/browse/JBDS-4139
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.2.0.AM3
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.2.0.AM3
>
>
> In the install log, I found this:
> {noformat}
> Tue, 25 Oct 2016 20:37:08 GMT-INFO: cdk - postVagrantSetup called
> Tue, 25 Oct 2016 20:37:08 GMT-INFO: undefined - Set PATH environment variable to c:\DevelopmentSuite\vagrant\bin;c:\DevelopmentSuite\cygwin\bin;'
> Tue, 25 Oct 2016 20:37:08 GMT-INFO: cdk - Execute command vagrant plugin install "c:\DevelopmentSuite\cdk\plugins\landrush-1.2.0.dev.gem"
> {noformat}
> I guess some method in cdk has an invalid reference to the CDKInstall.key()
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23208) SSLCertificatesPreference.isValid(String): Could not parse
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23208?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-23208:
---------------------------------------
[~adietish], no, I don't have that workspace anymore. So I cannot really confirm anything about the patch. I mean all I can verify is that it doesn't break things, but not that it fixes this issue that I had.
> SSLCertificatesPreference.isValid(String): Could not parse
> ----------------------------------------------------------
>
> Key: JBIDE-23208
> URL: https://issues.jboss.org/browse/JBIDE-23208
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.4.2.AM1
> Reporter: Martin Malina
> Fix For: 4.4.x
>
>
> When I start CDK and OpenShift connection is established, I get this in the Error Log view:
> org.jboss.tools.openshift.ui
> SSLCertificatesPreference.isValid(String): Could not parse 'Čt, 20 Zář 2018 12:54:07' in format E, d MMM yyyy HH:mm:ss
> An exception stack trace is not available.
> As you can see, the date is localized. I think this started happening after I updated to macOS Sierra last night - I never noticed it before. If we can figure out where the parsing is happening, perhaps we can come up with a switch for using english date here.
> Env:
> devstudio-10.2.0.AM1-v20160920-0457-B6061-installer-standalone.jar
> cdk 2.2.rc5
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[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 Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ]
Xavier Coulon edited comment on JBDS-4133 at 11/3/16 5:57 AM:
--------------------------------------------------------------
ok, so the PR that Jeff proposed fails, but I'd like to ask first: why do we have Lucene 5.4.1 rpms at first ? Can't we use the 5.2 version that is also available in Eclipse Orbit ? Then I would be able to upgrade the Webservices plugins to depend on that version of Lucene. If we have to use Lucene 5.4.1, can we consider adding the bundles in our Locus repo ?
For the record, Lucene is used to index JAX-RS elements in memory, so there is no impact if the lucene index format changed, since data is only available during the workbench session. Lucene indexes are re-built during the a full/clean build of a project.
was (Author: xcoulon):
ok, so the PR that Jeff proposed fails, but I'd like to ask first: why do we have Lucene 5.4.1 rpms at first ? Can't we use the 5.2 version that is also available in Eclipse Orbit ? Then I would be able to upgrade the Webservices plugins to depend on that version of Lucene.
For the record, Lucene is used to index JAX-RS elements in memory, so there is no impact if the lucene index format changed, since data is only available during the workbench session. Lucene indexes are re-built during the a full/clean build of a project.
> 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