Re: Problem compiling jsps after switching to 8.5.51
I reproduced this with a very basic project and created https://bz.apache.org/bugzilla/show_bug.cgi?id=64259 for it. Marek > Am 17.03.2020 um 14:43 schrieb Marek Neumann : > > > >> Am 17.03.2020 um 12:21 schrieb Mark Thomas : >> >> On 17/03/2020 09:29, Marek Neumann wrote: >>> Hi Mark, >>> >>> I tested with 8.5.53 and the problem still persists. Any idea what we can >>> do? >> >> Provide us with the simplest possible set of steps to recreate this so >> we can figure out what the root cause is. At a guess, you aren't using >> the EL API provided by the Apache Tomcat project. > > How can I verify this? Is it because the JspC is called directly from > jspc-maven-plugin? Which EL API is used in this case? > > This is the stacktrace: > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.eclipse.jetty:jetty-jspc-maven-plugin:9.4.24.v20191120:jspc (jspc) > on project ...: Failure processing jsps >at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:215) >at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:156) >at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:148) >at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) >at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) >at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) >at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) >at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) >at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) >at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) >at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) >at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) >at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) >at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) >at jdk.internal.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) >at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) >at java.lang.reflect.Method.invoke (Method.java:566) >at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:289) >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: org.apache.maven.plugin.MojoExecutionException: Failure processing > jsps >at org.eclipse.jetty.jspc.plugin.JspcMojo.execute (JspcMojo.java:278) >at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) >at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:210) >at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:156) >at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:148) >at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) >at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) >at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) >at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) >at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) >at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) >at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) >at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) >at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) >at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) >at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) >at jdk.internal.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) >at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) >at java.lang.reflect.Method.invoke (Method.java:566) >at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:2
Re: Problem compiling jsps after switching to 8.5.51
> Am 17.03.2020 um 12:21 schrieb Mark Thomas : > > On 17/03/2020 09:29, Marek Neumann wrote: >> Hi Mark, >> >> I tested with 8.5.53 and the problem still persists. Any idea what we can do? > > Provide us with the simplest possible set of steps to recreate this so > we can figure out what the root cause is. At a guess, you aren't using > the EL API provided by the Apache Tomcat project. How can I verify this? Is it because the JspC is called directly from jspc-maven-plugin? Which EL API is used in this case? This is the stacktrace: org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.jetty:jetty-jspc-maven-plugin:9.4.24.v20191120:jspc (jspc) on project ...: Failure processing jsps at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:566) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) 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: org.apache.maven.plugin.MojoExecutionException: Failure processing jsps at org.eclipse.jetty.jspc.plugin.JspcMojo.execute (JspcMojo.java:278) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:566) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) 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: org.apache.tools.ant.BuildException: Generation completed with [17] errors in [43] milliseconds at org.apache.jasper.JspC.execute (JspC.java:1543) at org.eclipse.jetty.jspc.plugin.JspcMojo.compile (JspcMojo.java:347) at org.eclipse.jetty.jspc.plugin.JspcMojo.execute (JspcMojo.java:272) Thanks, Marek >
Re: Problem compiling jsps after switching to 8.5.51
Hi Mark, I tested with 8.5.53 and the problem still persists. Any idea what we can do? Thanks, Marek > Am 28.02.2020 um 12:36 schrieb Mark Thomas : > > On 28/02/2020 10:57, Marek Neumann wrote: >> After going to the latest 8.5 release we have problems with jasper compiling >> jsps: >> >> [WARNING] org.apache.jasper.JasperException: javax.el.ELException: Unable to >> find ExpressionFactory of type: # Licensed to the Apache Software Foundation >> (ASF) under one or more >> >> We are using jetty-jspc-maven-plugin in version 9.4.24 to compile. There was >> a change to service loading: >> https://github.com/apache/tomcat/commit/ef13eb8fd9962432d244a7aad9cd85998d4cd3b9#diff-305be246f9d4a2068624785e76ee06efR1 >> >> Somehow the apache expression implementation >> (org.apache.el.ExpressionFactoryImpl) cannot be found anymore. Is there >> anything that need to be changed in our setup? Going back to 8.5.50 for >> jasper-el solves the problem. > > This is likely the same as: > https://bz.apache.org/bugzilla/show_bug.cgi?id=64153 > > Waiting for 8.5.52 is probably the simplest solution. > > You should be OK to compile with 8.5.50 but run with 8.5.51 if you need to. > > Mark > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Problem compiling jsps after switching to 8.5.51
After going to the latest 8.5 release we have problems with jasper compiling jsps: [WARNING] org.apache.jasper.JasperException: javax.el.ELException: Unable to find ExpressionFactory of type: # Licensed to the Apache Software Foundation (ASF) under one or more We are using jetty-jspc-maven-plugin in version 9.4.24 to compile. There was a change to service loading: https://github.com/apache/tomcat/commit/ef13eb8fd9962432d244a7aad9cd85998d4cd3b9#diff-305be246f9d4a2068624785e76ee06efR1 Somehow the apache expression implementation (org.apache.el.ExpressionFactoryImpl) cannot be found anymore. Is there anything that need to be changed in our setup? Going back to 8.5.50 for jasper-el solves the problem. Thanks for help, Marek
