[JBoss JIRA] (JBDS-4154) JavaEE Web Project > Run As > Maven not working
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-4154?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-4154:
-----------------------------------
I've pushed a new build that fixes the issue, hopefully: http://download.eclipse.org/technology/m2e/milestones/1.7/1.7.1.20161104-...
> JavaEE Web Project > Run As > Maven not working
> -----------------------------------------------
>
> Key: JBDS-4154
> URL: https://issues.jboss.org/browse/JBDS-4154
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, maven, rpm, target-platform
> Affects Versions: 10.2.0.AM3
> Environment: RHEL7 64bit
> Reporter: Lukáš Valach
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 10.2.0.GA
>
>
> I am not able to use embedded Maven. When I try to run Maven clean (or whatever else) I get following error message in Console (nothing in Error log):
> {code}
> Exception in thread "main" java.lang.NoClassDefFoundError: org/slf4j/Logger
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
> at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
> at java.lang.Class.getMethod0(Class.java:3018)
> at java.lang.Class.getMethod(Class.java:1784)
> at org.codehaus.plexus.classworlds.launcher.Launcher.getEnhancedMainMethod(Launcher.java:172)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:268)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: java.lang.ClassNotFoundException: org.slf4j.Logger
> at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
> ... 10 more
> {code}
> Standalone maven installation works fine.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4162) unresolved bundles - slf4j
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4162?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4162:
----------------------------------
Latest version of http://download.eclipse.org/tools/orbit/downloads/drops2/S20161021172207/... is 1.1.2... and its MANIFEST.MF has:
{code}Fragment-Host: org.slf4j.api;bundle-version="[1.7.10,1.8)"
Provide-Capability: org.slf4j.impl;org.slf4j.impl=logback;version:Vers
ion="1.7.10"
Export-Package: org.slf4j.impl;x-internal:=true;version="1.7.10";uses:
="org.slf4j,org.slf4j.spi"
{code}
So that won't work with 1.7.4. :(
Can't find a newer version of ch.qos.logback.slf4j yet.
Who uses these?
*ch.qos.logback.slf4j_1.0.7*
* code recommenders, m2e.logback, otdt
* !who-uses_ch.qos.logback.slf4j_1.0.7.png|thumbnail!
*slf4j.impl.log4j12_1.7.2*
* jgit, egit, mylyn, otdt
* !who-uses_slf4j.impl.log4j12_1.7.2.png|thumbnail!
> unresolved bundles - slf4j
> ---------------------------
>
> Key: JBDS-4162
> URL: https://issues.jboss.org/browse/JBDS-4162
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Fix For: 10.2.0.GA
>
> Attachments: who-uses_ch.qos.logback.slf4j_1.0.7.png, who-uses_slf4j.impl.log4j12_1.7.2.png
>
>
> Vaclav said:
> {quote}
> Just an update on unresolved bundles. I looked at rh-eclipse46-devstudio-10.2-0.20161103.0650.el7.x86_64.rpm and the only ones are:
> ch.qos.logback.slf4j
> org.slf4j.impl.log4j12{quote}
> Both of those bundles declare
> {code}Fragment-Host: org.slf4j.api;bundle-version="[1.7.2,1.7.3)"{code}
> And since we're now using slf4j.api_1.7.4.jar, which has in its MANIFEST.MF:
> {code}
> Export-Package: org.slf4j;version=1.7.4, org.slf4j.spi;version=1.7.4,
> org.slf4j.helpers;version=1.7.4
> Import-Package: org.slf4j.impl;version=1.6.0;resolution:=optional
> Bundle-SymbolicName: slf4j.api
> {code}
> I suspect we need to find newer versions of those that can use slf4j 1.7.4 instead of 1.7.2.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4162) unresolved bundles - slf4j
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4162?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4162:
-----------------------------
Attachment: who-uses_ch.qos.logback.slf4j_1.0.7.png
who-uses_slf4j.impl.log4j12_1.7.2.png
> unresolved bundles - slf4j
> ---------------------------
>
> Key: JBDS-4162
> URL: https://issues.jboss.org/browse/JBDS-4162
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Fix For: 10.2.0.GA
>
> Attachments: who-uses_ch.qos.logback.slf4j_1.0.7.png, who-uses_slf4j.impl.log4j12_1.7.2.png
>
>
> Vaclav said:
> {quote}
> Just an update on unresolved bundles. I looked at rh-eclipse46-devstudio-10.2-0.20161103.0650.el7.x86_64.rpm and the only ones are:
> ch.qos.logback.slf4j
> org.slf4j.impl.log4j12{quote}
> Both of those bundles declare
> {code}Fragment-Host: org.slf4j.api;bundle-version="[1.7.2,1.7.3)"{code}
> And since we're now using slf4j.api_1.7.4.jar, which has in its MANIFEST.MF:
> {code}
> Export-Package: org.slf4j;version=1.7.4, org.slf4j.spi;version=1.7.4,
> org.slf4j.helpers;version=1.7.4
> Import-Package: org.slf4j.impl;version=1.6.0;resolution:=optional
> Bundle-SymbolicName: slf4j.api
> {code}
> I suspect we need to find newer versions of those that can use slf4j 1.7.4 instead of 1.7.2.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23465) Cannot install JBoss Tools Abridged into Eclipse Neon 1 JEE (remediation required)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23465?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-23465:
--------------------------------------
Assignee: Nick Boldt
I guess it should not be a problem for AM3, [~nickboldt]?
> Cannot install JBoss Tools Abridged into Eclipse Neon 1 JEE (remediation required)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-23465
> URL: https://issues.jboss.org/browse/JBIDE-23465
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform, updatesite
> Affects Versions: 4.4.2.AM2
> Environment: Fedora 24
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Attachments: RemediationPage.png, RemediationPageUpdate.png
>
>
> When I try to install JBoss Tools Abridged from [1| into eclipse-jee-neon-1a-linux-gtk-x86_64.tar.gz , I am shown a remediation screen.
> !RemediationPage.png|thumbnail!
> !RemediationPageUpdate.png|thumbnail!
> This is the original error message:
> {code:java}
> Your original request has been modified.
> "JavaScript Development Tools" will be ignored because a newer version is already installed.
> "Eclipse JSON Editors and Tools" will be ignored because a newer version is already installed.
> "WST JSON Core" will be ignored because a newer version is already installed.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609)
> Software currently installed: Code Recommenders for Java Developers 2.4.3.v20160913-0645 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160913-0645)
> Only one of the following can be installed at once:
> Code Recommenders Dependency Identification UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.coordinates.rcp 2.4.0.v20160607-1609)
> Code Recommenders Dependency Identification UI 2.4.3.v20160913-0645 (org.eclipse.recommenders.coordinates.rcp 2.4.3.v20160913-0645)
> Cannot satisfy dependency:
> From: Code Recommenders for Java Developers 2.4.3.v20160913-0645 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160913-0645)
> To: org.eclipse.recommenders.coordinates.rcp [2.4.3.v20160913-0645]
> Cannot satisfy dependency:
> From: Code Recommenders Snipmatch UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp 2.4.0.v20160607-1609)
> To: bundle org.eclipse.recommenders.coordinates.rcp [2.4.0,2.4.1)
> Cannot satisfy dependency:
> From: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609)
> To: org.eclipse.recommenders.snipmatch.rcp [2.4.0.v20160607-1609]
> {code}
> [1] http://download.jboss.org/jbosstools/neon/staging/updates/
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4085) slow initial start up of rh-eclipse46-devstudio - disable usage constraint checking?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4085?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4085:
----------------------------------
Discussion re: unresolved bundles moved to separate issue, JBDS-4162
> slow initial start up of rh-eclipse46-devstudio - disable usage constraint checking?
> ------------------------------------------------------------------------------------
>
> Key: JBDS-4085
> URL: https://issues.jboss.org/browse/JBDS-4085
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Fix For: 10.2.0.GA
>
> Attachments: disable-uses-by-default.patch, restart-after-installing-m2e-wtp-jsf-stuff-from-Central.txt, restart-after-installing-m2e-wtp-jsf-stuff-from-Central_full.txt, rh-eclipse46-devstudio10.2.log.20161028-1611.txt, unresolved-max.out, unresolved-mid.out, unresolved-min.out, workspace-max.log, workspace-mid.log, workspace-min.log
>
>
> Tested:
> * rh-eclipse46-devstudio-10.2-0.20161004.2205.el7.x86_64.rpm
> * rh-eclipse46 Beta (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-Beta-...)
> rh-eclipse46 has its own unresolved bundles (https://bugzilla.redhat.com/show_bug.cgi?id=1381820). But when you add rh-eclipse46-devstudio, the number of unresolved symbols increases quite dramatically and initial start up times also get worse. (I guess that the two problems can be connected so I file them together but feel free to split them if I'm mistaken).
> I'm attaching "ss -s INSTALLED" and workspace logs for several scenarios:
> * "min" in the name means minimal install rh-eclipse46-devstudio
> * "mid" is for "yum install rh-eclipse46 rh-eclipse46-devstudio"
> * "max" is for "yum install 'rh-eclipse46*'" - all the available RPMs, including devstudio
> As for start up times, it looks like devstudio adds ~80s for one particular machine (Xeon with 16 cores 2.40GHz, 16 GB RAM). For example:
> initial start of rh-eclipse46: 40s
> same as above with rh-eclipse46-devstudio: 120s
> initial start of rh-eclipse46* except devstudio: 50s
> same as above with rh-eclipse46-devstudio: 140s
> Roland Grunberg managed to improve initial start up times in rh-eclise46 a few weeks ago (https://bugzilla.redhat.com/show_bug.cgi?id=1362178#c17). I don't know it it helps here but I'm linking it anyway...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4162) unresolved bundles - slf4j
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4162?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4162:
-----------------------------
Description:
Vaclav said:
{quote}
Just an update on unresolved bundles. I looked at rh-eclipse46-devstudio-10.2-0.20161103.0650.el7.x86_64.rpm and the only ones are:
ch.qos.logback.slf4j
org.slf4j.impl.log4j12{quote}
Both of those bundles declare
{code}Fragment-Host: org.slf4j.api;bundle-version="[1.7.2,1.7.3)"{code}
And since we're now using slf4j.api_1.7.4.jar, which has in its MANIFEST.MF:
{code}
Export-Package: org.slf4j;version=1.7.4, org.slf4j.spi;version=1.7.4,
org.slf4j.helpers;version=1.7.4
Import-Package: org.slf4j.impl;version=1.6.0;resolution:=optional
Bundle-SymbolicName: slf4j.api
{code}
I suspect we need to find newer versions of those that can use slf4j 1.7.4 instead of 1.7.2.
was:
Tested:
* rh-eclipse46-devstudio-10.2-0.20161004.2205.el7.x86_64.rpm
* rh-eclipse46 Beta (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-Beta-...)
rh-eclipse46 has its own unresolved bundles (https://bugzilla.redhat.com/show_bug.cgi?id=1381820). But when you add rh-eclipse46-devstudio, the number of unresolved symbols increases quite dramatically and initial start up times also get worse. (I guess that the two problems can be connected so I file them together but feel free to split them if I'm mistaken).
I'm attaching "ss -s INSTALLED" and workspace logs for several scenarios:
* "min" in the name means minimal install rh-eclipse46-devstudio
* "mid" is for "yum install rh-eclipse46 rh-eclipse46-devstudio"
* "max" is for "yum install 'rh-eclipse46*'" - all the available RPMs, including devstudio
As for start up times, it looks like devstudio adds ~80s for one particular machine (Xeon with 16 cores 2.40GHz, 16 GB RAM). For example:
initial start of rh-eclipse46: 40s
same as above with rh-eclipse46-devstudio: 120s
initial start of rh-eclipse46* except devstudio: 50s
same as above with rh-eclipse46-devstudio: 140s
Roland Grunberg managed to improve initial start up times in rh-eclise46 a few weeks ago (https://bugzilla.redhat.com/show_bug.cgi?id=1362178#c17). I don't know it it helps here but I'm linking it anyway...
> unresolved bundles - slf4j
> ---------------------------
>
> Key: JBDS-4162
> URL: https://issues.jboss.org/browse/JBDS-4162
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Fix For: 10.2.0.GA
>
>
> Vaclav said:
> {quote}
> Just an update on unresolved bundles. I looked at rh-eclipse46-devstudio-10.2-0.20161103.0650.el7.x86_64.rpm and the only ones are:
> ch.qos.logback.slf4j
> org.slf4j.impl.log4j12{quote}
> Both of those bundles declare
> {code}Fragment-Host: org.slf4j.api;bundle-version="[1.7.2,1.7.3)"{code}
> And since we're now using slf4j.api_1.7.4.jar, which has in its MANIFEST.MF:
> {code}
> Export-Package: org.slf4j;version=1.7.4, org.slf4j.spi;version=1.7.4,
> org.slf4j.helpers;version=1.7.4
> Import-Package: org.slf4j.impl;version=1.6.0;resolution:=optional
> Bundle-SymbolicName: slf4j.api
> {code}
> I suspect we need to find newer versions of those that can use slf4j 1.7.4 instead of 1.7.2.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4162) unresolved bundles - slf4j
by Nick Boldt (JIRA)
Nick Boldt created JBDS-4162:
--------------------------------
Summary: unresolved bundles - slf4j
Key: JBDS-4162
URL: https://issues.jboss.org/browse/JBDS-4162
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: rpm
Reporter: Václav Kadlčík
Assignee: Nick Boldt
Fix For: 10.2.0.GA
Tested:
* rh-eclipse46-devstudio-10.2-0.20161004.2205.el7.x86_64.rpm
* rh-eclipse46 Beta (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-Beta-...)
rh-eclipse46 has its own unresolved bundles (https://bugzilla.redhat.com/show_bug.cgi?id=1381820). But when you add rh-eclipse46-devstudio, the number of unresolved symbols increases quite dramatically and initial start up times also get worse. (I guess that the two problems can be connected so I file them together but feel free to split them if I'm mistaken).
I'm attaching "ss -s INSTALLED" and workspace logs for several scenarios:
* "min" in the name means minimal install rh-eclipse46-devstudio
* "mid" is for "yum install rh-eclipse46 rh-eclipse46-devstudio"
* "max" is for "yum install 'rh-eclipse46*'" - all the available RPMs, including devstudio
As for start up times, it looks like devstudio adds ~80s for one particular machine (Xeon with 16 cores 2.40GHz, 16 GB RAM). For example:
initial start of rh-eclipse46: 40s
same as above with rh-eclipse46-devstudio: 120s
initial start of rh-eclipse46* except devstudio: 50s
same as above with rh-eclipse46-devstudio: 140s
Roland Grunberg managed to improve initial start up times in rh-eclise46 a few weeks ago (https://bugzilla.redhat.com/show_bug.cgi?id=1362178#c17). I don't know it it helps here but I'm linking it anyway...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4149) Run Browsersim > java.lang.NoClassDefFoundError: javax/servlet/Servlet on exit
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4149?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-4149:
--------------------------------
Assignee: Ilya Buziuk (was: Nick Boldt)
> Run Browsersim > java.lang.NoClassDefFoundError: javax/servlet/Servlet on exit
> ------------------------------------------------------------------------------
>
> Key: JBDS-4149
> URL: https://issues.jboss.org/browse/JBDS-4149
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: browsersim, maven, rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL7 64bit
> Reporter: Lukáš Valach
> Assignee: Ilya Buziuk
> Priority: Critical
> Fix For: 10.2.0.GA
>
> Attachments: browsersim-error-on-close.png, ClassNotFoundEx_20161102_095940.png, eclipse.log, eclipse_10.2-0.20161101.1258.log, javax.servlet.310rpm_vs_orbit.png, rh-eclipse46-devstudio-snapshots-10_2.repo, rh-eclipse46-devstudio10.2.log.20161102-1855.txt, rh-eclipse46.repo
>
>
> I launch the browsersim (from Quick Access > Run Browsersim), and then exit the sim (right-click > Close), this error appears:
> !browsersim-error-on-close.png|thumbnail!
> {code}
> javax/servlet/Servlet
> Stack trace:
> java.lang.NoClassDefFoundError: javax/servlet/Servlet
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.jboss.tools.browsersim.ui.util.ReflectionUtil.call(ReflectionUtil.java:21)
> at org.jboss.tools.browsersim.ui.BrowserSim$3.widgetDisposed(BrowserSim.java:201)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:124)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1366)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1345)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1153)
> at org.eclipse.swt.widgets.Control.release(Control.java:3988)
> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:479)
> at org.eclipse.swt.widgets.Shell.dispose(Shell.java:2666)
> at org.eclipse.swt.widgets.Shell.closeWidget(Shell.java:670)
> at org.eclipse.swt.widgets.Shell.close(Shell.java:665)
> at org.jboss.tools.browsersim.ui.menu.BrowserSimMenuCreator$9.widgetSelected(BrowserSimMenuCreator.java:263)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143)
> at org.jboss.tools.browsersim.ui.launch.BrowserSimRunner.main(BrowserSimRunner.java:127)
> Caused by: java.lang.ClassNotFoundException: javax.servlet.Servlet
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 24 more
> {code}
> So... Maybe another javax.servlet requirement that's not properly defined?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4157) Validation doesn't work - NoClassDefFoundError: jdk/nashorn/internal/runtime/ECMAException
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4157?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4157 at 11/4/16 1:35 PM:
-----------------------------------------------------------
A. Install these rpms:
* rh-java-common-httpcomponents-client-4.3.6-1.4.el7.noarch.rpm
* rh-java-common-httpcomponents-client-cache-4.3.6-1.4.el7.noarch.rpm
* rh-eclipse46-eclipse-platform-4.6.1-2.4.el7.x86_64.rpm
* rh-eclipse46-eclipse-swt-4.6.1-2.4.el7.x86_64.rpm
* rh-eclipse46-eclipse-jdt-4.6.1-2.4.el7.noarch.rpm
* rh-eclipse46-eclipse-pde-4.6.1-2.4.el7.x86_64.rpm
* rh-eclipse46-eclipse-p2-discovery-4.6.1-2.4.el7.noarch.rpm
* rh-eclipse46-eclipse-equinox-osgi-4.6.1-2.4.el7.x86_64.rpm
* rh-eclipse46-eclipse-debuginfo-4.6.1-2.4.el7.x86_64.rpm
* rh-eclipse46-eclipse-contributor-tools-4.6.1-2.4.el7.x86_64.rpm
* rh-eclipse46-eclipse-tests-4.6.1-2.4.el7.x86_64.rpm
B. Update to the latest devstudio rpm - rh-eclipse46-devstudio-10.2-0.20161104.1527.el7.x86_64
1. CTRL-N > Project > name = foobar
2. select project folder
3. File > Import > General > Archive File > /home/nboldt/tmp/jboss-as-kitchensink-html5-mobile.zip
* into folder: foobar
{color:#14892c}*Cannot reproduce the above ECMAException.*{color}
1. Central > HTML5 Project quickstart
{color:#14892c}*Cannot reproduce the above ECMAException.*{color}
Curiously, your noted class, test.RestService, is not in the current version of the quickstart. It's also not having any validation problems for me.
!nope.png|thumbnail!
was (Author: nickboldt):
A. Install these rpms:
* rh-java-common-httpcomponents-client-4.3.6-1.4.el7.noarch.rpm
* rh-java-common-httpcomponents-client-cache-4.3.6-1.4.el7.noarch.rpm
* rh-eclipse46-eclipse-platform-4.6.1-2.4.el7.x86_64.rpm
* rh-eclipse46-eclipse-swt-4.6.1-2.4.el7.x86_64.rpm
* rh-eclipse46-eclipse-jdt-4.6.1-2.4.el7.noarch.rpm
* rh-eclipse46-eclipse-pde-4.6.1-2.4.el7.x86_64.rpm
* rh-eclipse46-eclipse-p2-discovery-4.6.1-2.4.el7.noarch.rpm
* rh-eclipse46-eclipse-equinox-osgi-4.6.1-2.4.el7.x86_64.rpm
* rh-eclipse46-eclipse-debuginfo-4.6.1-2.4.el7.x86_64.rpm
* rh-eclipse46-eclipse-contributor-tools-4.6.1-2.4.el7.x86_64.rpm
* rh-eclipse46-eclipse-tests-4.6.1-2.4.el7.x86_64.rpm
B. Update to the latest devstudio rpm - rh-eclipse46-devstudio-10.2-0.20161104.1527.el7.x86_64
1. CTRL-N > Project > name = foobar
2. select project folder
3. File > Import > General > Archive File > /home/nboldt/tmp/jboss-as-kitchensink-html5-mobile.zip
* into folder: foobar
{color:#14892c}*Cannot reproduce the above ECMAException.*{color}
1. Central > HTML5 Project quickstart
{color:#14892c}*Cannot reproduce the above ECMAException.*{color}
> Validation doesn't work - NoClassDefFoundError: jdk/nashorn/internal/runtime/ECMAException
> ------------------------------------------------------------------------------------------
>
> Key: JBDS-4157
> URL: https://issues.jboss.org/browse/JBDS-4157
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm, webservices
> Affects Versions: 10.2.0.AM3
> Environment: RHEL7, 64bit
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 10.2.0.GA
>
> Attachments: eclipse_log_ECMAException.txt, jboss-as-kitchensink-html5-mobile.zip, nope.png
>
>
> I notice that devstudio isn't able to validate rest service class. There is following error in the log.
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2016-11-03 11:52:21.836
> !MESSAGE An internal error occurred during: "Validating jboss-as-kitchensink-html5-mobile".
> !STACK 0
> java.lang.NoClassDefFoundError: jdk/nashorn/internal/runtime/ECMAException
> at org.eclipse.wst.jsdt.core.dom.ASTParser.internalCreateAST(ASTParser.java:903)
> at org.eclipse.wst.jsdt.core.dom.ASTParser.createAST(ASTParser.java:673)
> at org.eclipse.wst.jsdt.internal.core.validation.JavaScriptValidator.validate(JavaScriptValidator.java:62)
> at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at org.eclipse.wst.validation.internal.ValBuilderJob$Visitor.visit(ValBuilderJob.java:299)
> at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:120)
> at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:84)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:129)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:94)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:52)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:117)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:105)
> at org.eclipse.wst.validation.internal.ValBuilderJob.fullBuild(ValBuilderJob.java:219)
> at org.eclipse.wst.validation.internal.ValBuilderJob.run(ValBuilderJob.java:178)
> at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:126)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: jdk.nashorn.internal.runtime.ECMAException cannot be found by org.eclipse.wst.jsdt.core_2.0.0.v201610121400
> 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)
> ... 27 more
> {code}
> There are also errors like this
> {code}
> java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
> {code}
> I know that lucene is known issue but what about ECMAException?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4157) Validation doesn't work - NoClassDefFoundError: jdk/nashorn/internal/runtime/ECMAException
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4157?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4157:
-----------------------------
Attachment: nope.png
> Validation doesn't work - NoClassDefFoundError: jdk/nashorn/internal/runtime/ECMAException
> ------------------------------------------------------------------------------------------
>
> Key: JBDS-4157
> URL: https://issues.jboss.org/browse/JBDS-4157
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm, webservices
> Affects Versions: 10.2.0.AM3
> Environment: RHEL7, 64bit
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 10.2.0.GA
>
> Attachments: eclipse_log_ECMAException.txt, jboss-as-kitchensink-html5-mobile.zip, nope.png
>
>
> I notice that devstudio isn't able to validate rest service class. There is following error in the log.
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2016-11-03 11:52:21.836
> !MESSAGE An internal error occurred during: "Validating jboss-as-kitchensink-html5-mobile".
> !STACK 0
> java.lang.NoClassDefFoundError: jdk/nashorn/internal/runtime/ECMAException
> at org.eclipse.wst.jsdt.core.dom.ASTParser.internalCreateAST(ASTParser.java:903)
> at org.eclipse.wst.jsdt.core.dom.ASTParser.createAST(ASTParser.java:673)
> at org.eclipse.wst.jsdt.internal.core.validation.JavaScriptValidator.validate(JavaScriptValidator.java:62)
> at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at org.eclipse.wst.validation.internal.ValBuilderJob$Visitor.visit(ValBuilderJob.java:299)
> at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:120)
> at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:84)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:129)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:94)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:52)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:117)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:105)
> at org.eclipse.wst.validation.internal.ValBuilderJob.fullBuild(ValBuilderJob.java:219)
> at org.eclipse.wst.validation.internal.ValBuilderJob.run(ValBuilderJob.java:178)
> at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:126)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: jdk.nashorn.internal.runtime.ECMAException cannot be found by org.eclipse.wst.jsdt.core_2.0.0.v201610121400
> 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)
> ... 27 more
> {code}
> There are also errors like this
> {code}
> java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
> {code}
> I know that lucene is known issue but what about ECMAException?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months