AW: Struts 2.4

2018-04-16 Thread Christoph.Nenning
Maybe different minor versions of jdk, maven or maven-compiler-plugin ?


Regards,
Christoph



> -Ursprüngliche Nachricht-
> Von: Lukasz Lenart [mailto:lukaszlen...@apache.org]
> Gesendet: Montag, 16. April 2018 09:15
> An: Struts Developers List 
> Betreff: Re: Struts 2.4
> 
> Hm... it doesn't work with Jenkins and Java 6, but works locally (no
> idea what's the difference). The error is below
> 
> https://builds.apache.org/view/S-Z/view/Struts/job/Struts-2-4-
> JDK6/36/console
> 
> 
> [INFO] Compiling 4 source files to
> /home/jenkins/jenkins-slave/workspace/Struts-2-4-
> JDK6/apps/blank/target/classes
> An exception has occurred in the compiler (1.6.0_45). Please file a
> bug at the Java Developer Connection
> (http://java.sun.com/webapps/bugreport)  after checking the Bug Parade
> for duplicates. Include your program and the following diagnostic in
> your report.  Thank you.
> java.lang.LinkageError: loader constraint violation: when resolving
> method
> "com.sun.tools.javadoc.DocCommentScanner$Factory.preRegister(Lcom/su
> n/tools/javac/util/Context;)V"
> the class loader (instance of java/net/FactoryURLClassLoader) of the
> current class, com/sun/tools/javac/main/JavaCompiler, and the class
> loader (instance of sun/misc/Launcher$AppClassLoader) for resolved
> class, com/sun/tools/javadoc/DocCommentScanner$Factory, have different
> Class objects for the type com/sun/tools/javac/util/Context used in
> the signature
> at
> com.sun.tools.javac.main.JavaCompiler.initProcessAnnotations(JavaCompile
> r.java:883)
> at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:724)
> at com.sun.tools.javac.main.Main.compile(Main.java:353)
> at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:113)
> at
> org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(J
> avaxToolsCompiler.java:126)
> at
> org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCo
> mpiler.java:174)
> at
> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(Abstract
> CompilerMojo.java:943)
> at
> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.ja
> va:137)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
> BuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.ja
> va:209)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.ja
> va:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.ja
> va:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Life
> cycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Life
> cycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(Lif
> ecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter
> .java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> ava:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launch
> er.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:23
> 0)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Laun
> cher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352
> )
> 
> 
> 
> 2018-04-15 21:40 GMT+02:00 Lukasz Lenart :
> > Finally I have a stable build on Java 7, but maybe I can try with Java 6
> > https://builds.apache.org/view/S-Z/view/Struts/job/Struts-2-4-JDK7/
> >
> > 2018-04-06 9:46 GMT+02:00  :
> >> Hi,
> >>
> >> my impression is that there are lots of people using old versions of 
> >> struts,
> java, app servers, ... and who are not active on mailing-lists or github or
> whatever. Just when they have issues due to old versions being no longer
> supported they start sending mails to users list or asking on stack overflow.
> >>
> >> Actually I would prefer to drop struts 2.3 and not start with 2.4. But I 
> >> think
> there is much demand for it. And when we support old struts version it
> should depend on old java, too.
> >>
> >> Regards,
> >> Christoph
> >>
> >>
> >>> -Ursprüngliche Nachricht-
> >>> Von: Louis Smith [mailto:dr.louis.sm...@gmail.com]
> >>> Gesendet: Freitag, 30. März 2018 15:07
> >>> An: Struts 

AW: Struts 2.4

2018-04-06 Thread Christoph.Nenning
Hi,

my impression is that there are lots of people using old versions of struts, 
java, app servers, ... and who are not active on mailing-lists or github or 
whatever. Just when they have issues due to old versions being no longer 
supported they start sending mails to users list or asking on stack overflow.

Actually I would prefer to drop struts 2.3 and not start with 2.4. But I think 
there is much demand for it. And when we support old struts version it should 
depend on old java, too.

Regards,
Christoph


> -Ursprüngliche Nachricht-
> Von: Louis Smith [mailto:dr.louis.sm...@gmail.com]
> Gesendet: Freitag, 30. März 2018 15:07
> An: Struts Developers List 
> Betreff: Re: Struts 2.4
> 
> Considering that Java 8, 9, and 10 are all out - moving up to 7 seems like
> "not enough".
> 
> How about a tech survey of Struts users to see what Java version they are
> on?  I have my clients on Java 8, and doing research on 9.
> 
> Louis
> 
> Louis
> 
> 
> On Fri, Mar 30, 2018 at 8:10 AM, Lukasz Lenart 
> wrote:
> 
> > Hi,
> >
> > I thought about that for a long time and I think if we want to support
> > 2.3.x branch we must switch to Java 7 for it. Jenkins at Apache
> > doesn't support Java 6 anymore (at least I do not know how to make it
> > work).
> >
> > wdyt?
> >
> >
> > Regards
> > --
> > Łukasz
> > + 48 606 323 122 http://www.lenart.org.pl/
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> > For additional commands, e-mail: dev-h...@struts.apache.org
> >
> >