Yes, supported wasn't added to 2.3.x. Try trunk or 2.2.x On Wed, Mar 11, 2015 at 8:44 AM, Hal Hildebrand <hal.hildebr...@me.com> wrote:
> Sorry, this fell out of my inbox. > > I'm using 2.3.0 and JDK 1.8 and maven. If I change the target to 1.8 from > 1.7, I get: > > java.lang.IllegalArgumentException > at org.apache.xbean.asm4.ClassReader.<init>(Unknown Source) > at org.apache.xbean.asm4.ClassReader.<init>(Unknown Source) > at org.apache.xbean.asm4.ClassReader.<init>(Unknown Source) > at > org.apache.openjpa.enhance.AsmAdaptor.toJava7ByteArray(AsmAdaptor.java:93) > at > org.apache.openjpa.enhance.AsmAdaptor.writeJava7(AsmAdaptor.java:84) > at org.apache.openjpa.enhance.AsmAdaptor.write(AsmAdaptor.java:54) > at > org.apache.openjpa.enhance.PCEnhancer.record(PCEnhancer.java:633) > at > org.apache.openjpa.enhance.PCEnhancer.record(PCEnhancer.java:619) > at org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:4900) > at > org.apache.openjpa.ant.PCEnhancerTask.executeOn(PCEnhancerTask.java:89) > at > org.apache.openjpa.lib.ant.AbstractTask.execute(AbstractTask.java:184) > at > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) > at org.apache.tools.ant.Task.perform(Task.java:348) > at org.apache.tools.ant.Target.execute(Target.java:390) > at org.apache.tools.ant.Target.performTasks(Target.java:411) > at > org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399) > at org.apache.tools.ant.Project.executeTarget(Project.java:1368) > at > org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:327) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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) > > > On Mar 9, 2015, at 11:30 AM, Rick Curtis <curti...@gmail.com> wrote: > > > > Hal - > > > > What are you seeing for problems? We've done some amount of testing > Entity > > enhancement when using java 8 language features. > > > > Thanks, > > Rick > > > > On Mon, Mar 9, 2015 at 10:46 AM, Hal Hildebrand <hal.hildebr...@me.com> > > wrote: > > > >> No. > >> > >>> On Mar 9, 2015, at 8:44 AM, Boblitz John <john.bobl...@bertschi.com> > >> wrote: > >>> > >>> Hello, > >>> > >>> Does the Byte Code Enhancement work when compiled for 1.8? > >>> > >>> Thanks & Regards, > >>> > >>> John Boblitz > >>> > >>> > >>>> -----Original Message----- > >>>> From: Hal Hildebrand [mailto:hal.hildebr...@me.com] > >>>> Sent: Montag, 9. März 2015 16:21 > >>>> To: users@openjpa.apache.org > >>>> Subject: Re: Java 8/Java 7 end of life > >>>> > >>>> I can certainly confirm that OpenJPA runs on java 8. And even > compiles > >>>> when using source 1.7, target 1.7. Byte code enhancement works fine > on > >> the > >>>> code when compiled in that fashion. > >>>> > >>>>> On Mar 9, 2015, at 6:06 AM, Rick Curtis <curti...@gmail.com> wrote: > >>>>> > >>>>> OpenJPA 2.3.x and trunk should be functional with java8, but I don't > >>>>> think you can build OpenJPA with java8. > >>>>> > >>>>> On Mon, Mar 9, 2015 at 3:52 AM, Henno Vermeulen > >>>>> <he...@huizemolenaar.nl> > >>>>> wrote: > >>>>> > >>>>>> Hello, > >>>>>> > >>>>>> AFAIK, OpenJPA still doesn't work with Java 8. Are there any plans > of > >>>>>> fixing this soon? Perhaps OpenJPA committers could give this some > >>>>>> more priority? > >>>>>> > >>>>>> Oracle public support for Java 7 will end after April this year, see > >>>>>> http://www.oracle.com/technetwork/java/javase/eol-135779.html > >>>>>> If I understand well, this means that security issues in Oracle's > >>>>>> Java 7 runtime will no longer be fixed so that an application using > >>>>>> OpenJPA on Java 7 will become more and more vulnerable over time. > >>>>>> > >>>>>> The ticket for Java 8 was last updated in October 2014: > >>>>>> https://issues.apache.org/jira/browse/OPENJPA-2386 > >>>>>> > >>>>>> Regards, > >>>>>> Henno Vermeulen > >>>>>> > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> *Rick Curtis* > >>> > >> > >> > > > > > > -- > > *Rick Curtis* > > -- *Rick Curtis*
