>From my POV probably early spring next year. I'd like to cut new major
releases of Santuario (switch to using CXF's StaxUtils for DOM parsing) +
WSS4J (switch to a new major version of ehcache / jcache).

Colm.

On Fri, Sep 28, 2018 at 5:23 PM David Karlsen <[email protected]>
wrote:

> When will CXF 3.3 be cut - this is the missing piece in our puzzle to be
> java11 ready.
>
> ---------- Forwarded message ---------
> From: Dennis Kieselhorst (JIRA) <[email protected]>
> Date: fre. 28. sep. 2018 kl. 16:26
> Subject: [jira] [Commented] (CXF-7852) Cannot generate code on jdk 11
> To: <[email protected]>
>
>
>
>     [
>
> https://issues.apache.org/jira/browse/CXF-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16631920#comment-16631920
> ]
>
> Dennis Kieselhorst commented on CXF-7852:
> -----------------------------------------
>
> We don't have an ETA yet, but you can start the discussion on the
> mailinglist: https://lists.apache.org/[email protected]
>
> > Cannot generate code on jdk 11
> > ------------------------------
> >
> >                 Key: CXF-7852
> >                 URL: https://issues.apache.org/jira/browse/CXF-7852
> >             Project: CXF
> >          Issue Type: Bug
> >          Components: Tooling
> >    Affects Versions: 3.2.6
> >            Reporter: David J. M. Karlsen
> >            Assignee: Freeman Fang
> >            Priority: Major
> >             Fix For: 3.3.0
> >
> >
> > the codegen maven plugin seems to add an non-existing module when running
> on java11:
> > {noformat}
> > [INFO] --- cxf-codegen-plugin:3.2.6:wsdl2java (default) @ jfr-srv-schemas
> ---
> > [INFO] Using proxy server configured in maven.
> > [INFO] Running code generation in fork mode...
> > [INFO] The java executable is
> /Library/Java/JavaVirtualMachines/openjdk-11.jdk/Contents/Home/bin/java
> > [INFO] Building jar:
>
> /var/folders/c7/18m1hlzs075_z0f5nfnt44jm0000gn/T/cxf-tmp-2107463654183740055/cxf-codegen14725056335928137302.jar
> > [INFO] Error occurred during initialization of boot layer
> > [INFO] java.lang.module.FindException: Module java.xml.ws not found
> > {noformat}
> > {noformat}
> > Command line was:
> /Library/Java/JavaVirtualMachines/openjdk-11.jdk/Contents/Home/bin/java
> --add-modules java.activation,java.xml.bind,java.xml.ws
>
> --add-exports=java.xml.bind/com.sun.xml.internal.bind.v2.runtime=ALL-UNNAMED
> --add-exports=jdk.xml.dom/org.w3c.dom.html=ALL-UNNAMED
>
> --add-exports=java.xml/com.sun.org.apache.xerces.internal.impl.xs=ALL-UNNAMED
>
> --add-exports=java.xml.bind/com.sun.xml.internal.bind.marshaller=ALL-UNNAMED
> --add-opens java.xml.ws/javax.xml.ws.wsaddressing=ALL-UNNAMED --add-opens
> java.base/java.security=ALL-UNNAMED --add-opens java.base/java.net
> =ALL-UNNAMED
> --add-opens java.base/java.lang=ALL-UNNAMED --add-opens
> java.base/java.util=ALL-UNNAMED --add-opens
> java.base/java.util.concurrent=ALL-UNNAMED -jar
>
> /var/folders/c7/18m1hlzs075_z0f5nfnt44jm0000gn/T/cxf-tmp-2107463654183740055/cxf-codegen14725056335928137302.jar
>
> /var/folders/c7/18m1hlzs075_z0f5nfnt44jm0000gn/T/cxf-tmp-2107463654183740055/cxf-w2j4026495259386863606args
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> >     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:954)
> >     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:
> > Exit code: 1
> > {noformat}
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)
>
>
> --
> --
> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
>


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Reply via email to