You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by David Blevins <da...@gmail.com> on 2014/04/01 05:02:56 UTC
Java 8 and possible TomEE 1.7.0
Romain had pinged me offline about the idea of upgrading our ASM dependencies to v5 so we could support Java 8 (code compiled in Java 8 can't be read by ASM v4 or earlier).
This combined with the Mojarra and EclipseLink / Plume distribution seem like good features for a 1.7.0
We also have the quartz repackaging we did which are not quite "minor" patch changes.
Any thoughts on updating the trunk version to 1.7?
-David
Re: Java 8 and possible TomEE 1.7.0
Posted by agumbrecht <ag...@tomitribe.com>.
Fixed in 1.7.x and trunk
https://issues.apache.org/jira/browse/TOMEE-1391
<pluginManagement>
<plugins>
....
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-remote-resources-plugin</artifactId>
<version>1.5</version>
<dependencies>
<dependency>
<groupId>org.apache.maven.shared</groupId>
<artifactId>maven-filtering</artifactId>
<version>1.2</version>
</dependency>
</dependencies>
</plugin>
Andy.
-----
--
Andy Gumbrecht
http://www.tomitribe.com
agumbrecht@tomitribe.com
https://twitter.com/AndyGeeDe
TomEE treibt Tomitribe ! | http://tomee.apache.org
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4672199.html
Sent from the TomEE Dev mailing list archive at Nabble.com.
Re: Java 8 and possible TomEE 1.7.0
Posted by Romain Manni-Bucau <rm...@gmail.com>.
add it as dependency of the remote resources plugin (think this is the one):
<plugin>
.....
<dependencies>
here
</dependencies>
</plugin>
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-07-01 12:16 GMT+02:00 san <sa...@linuxmail.org>:
> how can i force maven to use latest version of maven-filtering 1.2 when
> compiling TomEE with java8? i insert the dependency configuration in
> pom.xml
> <dependency>
> <groupId>org.apache.maven.shared</groupId>
> <artifactId>maven-filtering</artifactId>
> <version>1.2</version>
> </dependency>
> after placing the dependency configuration it download the 1.2 version but
> also downloading the older version 1.1 and compiling tomEE with 1.1
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4670251.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
Re: Java 8 and possible TomEE 1.7.0
Posted by san <sa...@linuxmail.org>.
how can i force maven to use latest version of maven-filtering 1.2 when
compiling TomEE with java8? i insert the dependency configuration in
pom.xml
<dependency>
<groupId>org.apache.maven.shared</groupId>
<artifactId>maven-filtering</artifactId>
<version>1.2</version>
</dependency>
after placing the dependency configuration it download the 1.2 version but
also downloading the older version 1.1 and compiling tomEE with 1.1
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4670251.html
Sent from the TomEE Dev mailing list archive at Nabble.com.
Re: Java 8 and possible TomEE 1.7.0
Posted by Romain Manni-Bucau <rm...@gmail.com>.
If it is not release a mail on maven list would be a good start, if it is
just send us a patch we'll apply it happily
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-06-26 16:15 GMT+02:00 san <sa...@linuxmail.org>:
> I'm stuck at one point when compiling the tomEE with java8. I am using the
> bug fixed version of maven-filtering [1] and compiled/install that plugin
> to
> m2 repository. maven always use the older version to compile the tomee
> instead the newer version of maven-filtering. is there a way i can push to
> use the latest version of maven-filtering which i compiled?
>
>
> [1]http://svn.apache.org/viewvc?view=revision&revision=r1563467
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4670205.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>
Re: Java 8 and possible TomEE 1.7.0
Posted by san <sa...@linuxmail.org>.
I'm stuck at one point when compiling the tomEE with java8. I am using the
bug fixed version of maven-filtering [1] and compiled/install that plugin to
m2 repository. maven always use the older version to compile the tomee
instead the newer version of maven-filtering. is there a way i can push to
use the latest version of maven-filtering which i compiled?
[1]http://svn.apache.org/viewvc?view=revision&revision=r1563467
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4670205.html
Sent from the TomEE Dev mailing list archive at Nabble.com.
Re: Java 8 and possible TomEE 1.7.0
Posted by san <sa...@linuxmail.org>.
its the same error which Nikki shared.
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4670189.html
Sent from the TomEE Dev mailing list archive at Nabble.com.
Re: Java 8 and possible TomEE 1.7.0
Posted by Romain Manni-Bucau <rm...@gmail.com>.
FYI http://jira.codehaus.org/browse/MSHARED-319
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-06-25 17:08 GMT+02:00 Niki Dokovski <ni...@gmail.com>:
> Ok Thanks
>
>
> On Wed, Jun 25, 2014 at 6:03 PM, Romain Manni-Bucau <rmannibucau@gmail.com
> >
> wrote:
>
> > Oh recall this one.
> >
> > It is known by maven team (there is a jira somewhere). This is fixed on
> > trunk IIRC, not sure it was released or not
> >
> >
> >
> > Romain Manni-Bucau
> > Twitter: @rmannibucau
> > Blog: http://rmannibucau.wordpress.com/
> > LinkedIn: http://fr.linkedin.com/in/rmannibucau
> > Github: https://github.com/rmannibucau
> >
> >
> > 2014-06-25 17:01 GMT+02:00 Niki Dokovski <ni...@gmail.com>:
> >
> > > Same issue here with jdk1.8.0_05 on mac os
> > >
> > > [ERROR] Failed to execute goal
> > > org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
> > > (default) on project apache-tomee: Error rendering velocity resource.
> > > NullPointerException -> [Help 1]
> > >
> > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute
> > > goal org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
> > > (default) on project apache-tomee: Error rendering velocity resource.
> > >
> > > at
> > >
> > >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> > >
> > > 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:483)
> > >
> > > 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: Error
> > rendering
> > > velocity resource.
> > >
> > > at
> > >
> > >
> >
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.processResourceBundles(ProcessRemoteResourcesMojo.java:1246)
> > >
> > > at
> > >
> > >
> >
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:520)
> > >
> > > at
> > >
> > >
> >
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
> > >
> > > at
> > >
> > >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> > >
> > > ... 19 more
> > >
> > > Caused by: java.lang.NullPointerException
> > >
> > > at java.util.Objects.requireNonNull(Objects.java:203)
> > >
> > > at java.util.ArrayList.removeAll(ArrayList.java:674)
> > >
> > > at
> > >
> > >
> >
> org.apache.maven.shared.filtering.DefaultMavenFileFilter.getDefaultFilterWrappers(DefaultMavenFileFilter.java:216)
> > >
> > > at
> > >
> > >
> >
> org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile(DefaultMavenFileFilter.java:84)
> > >
> > > at
> > >
> > >
> >
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.copyResourceIfExists(ProcessRemoteResourcesMojo.java:884)
> > >
> > > at
> > >
> > >
> >
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.processResourceBundles(ProcessRemoteResourcesMojo.java:1139)
> > >
> > > ... 22 more
> > >
> > >
> > > On Wed, Jun 25, 2014 at 5:41 PM, Romain Manni-Bucau <
> > rmannibucau@gmail.com
> > > >
> > > wrote:
> > >
> > > > what does say -e? maybe a maven plugin doesn't work with java 8
> > > >
> > > >
> > > >
> > > > Romain Manni-Bucau
> > > > Twitter: @rmannibucau
> > > > Blog: http://rmannibucau.wordpress.com/
> > > > LinkedIn: http://fr.linkedin.com/in/rmannibucau
> > > > Github: https://github.com/rmannibucau
> > > >
> > > >
> > > > 2014-06-25 16:28 GMT+02:00 san <sa...@linuxmail.org>:
> > > >
> > > > > I tried to compile TomEE with JAVA8 but getting Build failed.
> > > > >
> > > > > [INFO] OpenEJB :: TomEE :: Apache TomEE .................. FAILURE
> > > > [1.409s]
> > > > > [INFO] OpenEJB :: TomEE :: Overlay Runner ................ SKIPPED
> > > > > [INFO]
> > > > >
> > >
> ------------------------------------------------------------------------
> > > > > [INFO] BUILD FAILURE
> > > > > [INFO]
> > > > >
> > >
> ------------------------------------------------------------------------
> > > > > [INFO] Total time: 2:44.511s
> > > > > [INFO] Finished at: Mon Jun 23 03:47:18 CEST 2014
> > > > > [INFO] Final Memory: 65M/215M
> > > > > [INFO]
> > > > >
> > >
> ------------------------------------------------------------------------
> > > > > [ERROR] Failed to execute goal
> > > > > org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
> > > > > (default)
> > > > > on project apache-tomee: Error rendering velocity resource.
> > > > > NullPointerException -> [Help 1]
> > > > > [ERROR]
> > > > > [ERROR] To see the full stack trace of the errors, re-run Maven
> with
> > > the
> > > > -e
> > > > > switch.
> > > > > [ERROR] Re-run Maven using the -X switch to enable full debug
> > logging.
> > > > > [ERROR]
> > > > > [ERROR] For more information about the errors and possible
> solutions,
> > > > > please
> > > > > read the following articles:
> > > > > [ERROR] [Help 1]
> > > > >
> > >
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> > > > > [ERROR]
> > > > > [ERROR] After correcting the problems, you can resume the build
> with
> > > the
> > > > > command
> > > > > [ERROR] mvn <goals> -rf :apache-tomee
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > View this message in context:
> > > > >
> > > >
> > >
> >
> http://tomee-openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4670183.html
> > > > > Sent from the TomEE Dev mailing list archive at Nabble.com.
> > > > >
> > > >
> > >
> >
>
Re: Java 8 and possible TomEE 1.7.0
Posted by Niki Dokovski <ni...@gmail.com>.
Ok Thanks
On Wed, Jun 25, 2014 at 6:03 PM, Romain Manni-Bucau <rm...@gmail.com>
wrote:
> Oh recall this one.
>
> It is known by maven team (there is a jira somewhere). This is fixed on
> trunk IIRC, not sure it was released or not
>
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-06-25 17:01 GMT+02:00 Niki Dokovski <ni...@gmail.com>:
>
> > Same issue here with jdk1.8.0_05 on mac os
> >
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
> > (default) on project apache-tomee: Error rendering velocity resource.
> > NullPointerException -> [Help 1]
> >
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> > goal org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
> > (default) on project apache-tomee: Error rendering velocity resource.
> >
> > at
> >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> >
> > 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:483)
> >
> > 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: Error
> rendering
> > velocity resource.
> >
> > at
> >
> >
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.processResourceBundles(ProcessRemoteResourcesMojo.java:1246)
> >
> > at
> >
> >
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:520)
> >
> > at
> >
> >
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
> >
> > at
> >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> >
> > ... 19 more
> >
> > Caused by: java.lang.NullPointerException
> >
> > at java.util.Objects.requireNonNull(Objects.java:203)
> >
> > at java.util.ArrayList.removeAll(ArrayList.java:674)
> >
> > at
> >
> >
> org.apache.maven.shared.filtering.DefaultMavenFileFilter.getDefaultFilterWrappers(DefaultMavenFileFilter.java:216)
> >
> > at
> >
> >
> org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile(DefaultMavenFileFilter.java:84)
> >
> > at
> >
> >
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.copyResourceIfExists(ProcessRemoteResourcesMojo.java:884)
> >
> > at
> >
> >
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.processResourceBundles(ProcessRemoteResourcesMojo.java:1139)
> >
> > ... 22 more
> >
> >
> > On Wed, Jun 25, 2014 at 5:41 PM, Romain Manni-Bucau <
> rmannibucau@gmail.com
> > >
> > wrote:
> >
> > > what does say -e? maybe a maven plugin doesn't work with java 8
> > >
> > >
> > >
> > > Romain Manni-Bucau
> > > Twitter: @rmannibucau
> > > Blog: http://rmannibucau.wordpress.com/
> > > LinkedIn: http://fr.linkedin.com/in/rmannibucau
> > > Github: https://github.com/rmannibucau
> > >
> > >
> > > 2014-06-25 16:28 GMT+02:00 san <sa...@linuxmail.org>:
> > >
> > > > I tried to compile TomEE with JAVA8 but getting Build failed.
> > > >
> > > > [INFO] OpenEJB :: TomEE :: Apache TomEE .................. FAILURE
> > > [1.409s]
> > > > [INFO] OpenEJB :: TomEE :: Overlay Runner ................ SKIPPED
> > > > [INFO]
> > > >
> > ------------------------------------------------------------------------
> > > > [INFO] BUILD FAILURE
> > > > [INFO]
> > > >
> > ------------------------------------------------------------------------
> > > > [INFO] Total time: 2:44.511s
> > > > [INFO] Finished at: Mon Jun 23 03:47:18 CEST 2014
> > > > [INFO] Final Memory: 65M/215M
> > > > [INFO]
> > > >
> > ------------------------------------------------------------------------
> > > > [ERROR] Failed to execute goal
> > > > org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
> > > > (default)
> > > > on project apache-tomee: Error rendering velocity resource.
> > > > NullPointerException -> [Help 1]
> > > > [ERROR]
> > > > [ERROR] To see the full stack trace of the errors, re-run Maven with
> > the
> > > -e
> > > > switch.
> > > > [ERROR] Re-run Maven using the -X switch to enable full debug
> logging.
> > > > [ERROR]
> > > > [ERROR] For more information about the errors and possible solutions,
> > > > please
> > > > read the following articles:
> > > > [ERROR] [Help 1]
> > > >
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> > > > [ERROR]
> > > > [ERROR] After correcting the problems, you can resume the build with
> > the
> > > > command
> > > > [ERROR] mvn <goals> -rf :apache-tomee
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > View this message in context:
> > > >
> > >
> >
> http://tomee-openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4670183.html
> > > > Sent from the TomEE Dev mailing list archive at Nabble.com.
> > > >
> > >
> >
>
Re: Java 8 and possible TomEE 1.7.0
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Oh recall this one.
It is known by maven team (there is a jira somewhere). This is fixed on
trunk IIRC, not sure it was released or not
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-06-25 17:01 GMT+02:00 Niki Dokovski <ni...@gmail.com>:
> Same issue here with jdk1.8.0_05 on mac os
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
> (default) on project apache-tomee: Error rendering velocity resource.
> NullPointerException -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
> (default) on project apache-tomee: Error rendering velocity resource.
>
> at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
>
> 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:483)
>
> 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: Error rendering
> velocity resource.
>
> at
>
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.processResourceBundles(ProcessRemoteResourcesMojo.java:1246)
>
> at
>
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:520)
>
> at
>
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
>
> at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>
> ... 19 more
>
> Caused by: java.lang.NullPointerException
>
> at java.util.Objects.requireNonNull(Objects.java:203)
>
> at java.util.ArrayList.removeAll(ArrayList.java:674)
>
> at
>
> org.apache.maven.shared.filtering.DefaultMavenFileFilter.getDefaultFilterWrappers(DefaultMavenFileFilter.java:216)
>
> at
>
> org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile(DefaultMavenFileFilter.java:84)
>
> at
>
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.copyResourceIfExists(ProcessRemoteResourcesMojo.java:884)
>
> at
>
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.processResourceBundles(ProcessRemoteResourcesMojo.java:1139)
>
> ... 22 more
>
>
> On Wed, Jun 25, 2014 at 5:41 PM, Romain Manni-Bucau <rmannibucau@gmail.com
> >
> wrote:
>
> > what does say -e? maybe a maven plugin doesn't work with java 8
> >
> >
> >
> > Romain Manni-Bucau
> > Twitter: @rmannibucau
> > Blog: http://rmannibucau.wordpress.com/
> > LinkedIn: http://fr.linkedin.com/in/rmannibucau
> > Github: https://github.com/rmannibucau
> >
> >
> > 2014-06-25 16:28 GMT+02:00 san <sa...@linuxmail.org>:
> >
> > > I tried to compile TomEE with JAVA8 but getting Build failed.
> > >
> > > [INFO] OpenEJB :: TomEE :: Apache TomEE .................. FAILURE
> > [1.409s]
> > > [INFO] OpenEJB :: TomEE :: Overlay Runner ................ SKIPPED
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > > [INFO] BUILD FAILURE
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > > [INFO] Total time: 2:44.511s
> > > [INFO] Finished at: Mon Jun 23 03:47:18 CEST 2014
> > > [INFO] Final Memory: 65M/215M
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > > [ERROR] Failed to execute goal
> > > org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
> > > (default)
> > > on project apache-tomee: Error rendering velocity resource.
> > > NullPointerException -> [Help 1]
> > > [ERROR]
> > > [ERROR] To see the full stack trace of the errors, re-run Maven with
> the
> > -e
> > > switch.
> > > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > > [ERROR]
> > > [ERROR] For more information about the errors and possible solutions,
> > > please
> > > read the following articles:
> > > [ERROR] [Help 1]
> > >
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> > > [ERROR]
> > > [ERROR] After correcting the problems, you can resume the build with
> the
> > > command
> > > [ERROR] mvn <goals> -rf :apache-tomee
> > >
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > >
> >
> http://tomee-openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4670183.html
> > > Sent from the TomEE Dev mailing list archive at Nabble.com.
> > >
> >
>
Re: Java 8 and possible TomEE 1.7.0
Posted by Niki Dokovski <ni...@gmail.com>.
Same issue here with jdk1.8.0_05 on mac os
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
(default) on project apache-tomee: Error rendering velocity resource.
NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
(default) on project apache-tomee: Error rendering velocity resource.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
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:483)
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: Error rendering
velocity resource.
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.processResourceBundles(ProcessRemoteResourcesMojo.java:1246)
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:520)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
Caused by: java.lang.NullPointerException
at java.util.Objects.requireNonNull(Objects.java:203)
at java.util.ArrayList.removeAll(ArrayList.java:674)
at
org.apache.maven.shared.filtering.DefaultMavenFileFilter.getDefaultFilterWrappers(DefaultMavenFileFilter.java:216)
at
org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile(DefaultMavenFileFilter.java:84)
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.copyResourceIfExists(ProcessRemoteResourcesMojo.java:884)
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.processResourceBundles(ProcessRemoteResourcesMojo.java:1139)
... 22 more
On Wed, Jun 25, 2014 at 5:41 PM, Romain Manni-Bucau <rm...@gmail.com>
wrote:
> what does say -e? maybe a maven plugin doesn't work with java 8
>
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-06-25 16:28 GMT+02:00 san <sa...@linuxmail.org>:
>
> > I tried to compile TomEE with JAVA8 but getting Build failed.
> >
> > [INFO] OpenEJB :: TomEE :: Apache TomEE .................. FAILURE
> [1.409s]
> > [INFO] OpenEJB :: TomEE :: Overlay Runner ................ SKIPPED
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] BUILD FAILURE
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time: 2:44.511s
> > [INFO] Finished at: Mon Jun 23 03:47:18 CEST 2014
> > [INFO] Final Memory: 65M/215M
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
> > (default)
> > on project apache-tomee: Error rendering velocity resource.
> > NullPointerException -> [Help 1]
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e
> > switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > [ERROR]
> > [ERROR] For more information about the errors and possible solutions,
> > please
> > read the following articles:
> > [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> > [ERROR]
> > [ERROR] After correcting the problems, you can resume the build with the
> > command
> > [ERROR] mvn <goals> -rf :apache-tomee
> >
> >
> >
> >
> > --
> > View this message in context:
> >
> http://tomee-openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4670183.html
> > Sent from the TomEE Dev mailing list archive at Nabble.com.
> >
>
Re: Java 8 and possible TomEE 1.7.0
Posted by Romain Manni-Bucau <rm...@gmail.com>.
what does say -e? maybe a maven plugin doesn't work with java 8
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-06-25 16:28 GMT+02:00 san <sa...@linuxmail.org>:
> I tried to compile TomEE with JAVA8 but getting Build failed.
>
> [INFO] OpenEJB :: TomEE :: Apache TomEE .................. FAILURE [1.409s]
> [INFO] OpenEJB :: TomEE :: Overlay Runner ................ SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 2:44.511s
> [INFO] Finished at: Mon Jun 23 03:47:18 CEST 2014
> [INFO] Final Memory: 65M/215M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
> (default)
> on project apache-tomee: Error rendering velocity resource.
> NullPointerException -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :apache-tomee
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4670183.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>
Re: Java 8 and possible TomEE 1.7.0
Posted by san <sa...@linuxmail.org>.
I tried to compile TomEE with JAVA8 but getting Build failed.
[INFO] OpenEJB :: TomEE :: Apache TomEE .................. FAILURE [1.409s]
[INFO] OpenEJB :: TomEE :: Overlay Runner ................ SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 2:44.511s
[INFO] Finished at: Mon Jun 23 03:47:18 CEST 2014
[INFO] Final Memory: 65M/215M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default)
on project apache-tomee: Error rendering velocity resource.
NullPointerException -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn <goals> -rf :apache-tomee
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4670183.html
Sent from the TomEE Dev mailing list archive at Nabble.com.
Re: Java 8 and possible TomEE 1.7.0
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
all right, [2] depend on guys I guess. CI uses mvn clean install
-Pall-adapters, dev uses the command of the page or some other maven
shortcuts I guess (I do at least). Feel free to ask anything more precise
if you feel lost, we'll try to help you to get familiar with the product.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-06-25 3:49 GMT+02:00 san <sa...@linuxmail.org>:
> I don't have any previous experience of working on TomEE. Maybe i will ask
> some silly questions.
>
> is this [1] the correct trunk link ?
> I have to follow this [2] guide to compile the code
>
> [1]http://svn.apache.org/repos/asf/tomee/tomee/trunk
> [2]http://tomee.apache.org/dev/source-code.html
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4670170.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>
Re: Java 8 and possible TomEE 1.7.0
Posted by san <sa...@linuxmail.org>.
I don't have any previous experience of working on TomEE. Maybe i will ask
some silly questions.
is this [1] the correct trunk link ?
I have to follow this [2] guide to compile the code
[1]http://svn.apache.org/repos/asf/tomee/tomee/trunk
[2]http://tomee.apache.org/dev/source-code.html
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4670170.html
Sent from the TomEE Dev mailing list archive at Nabble.com.
Re: Java 8 and possible TomEE 1.7.0
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
Only trunk supports Java 8 at the moment. Then the config depend where you
want to put it (tomcat ssl connector, cxf, elsewhere...)
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-06-24 19:06 GMT+02:00 san <sa...@linuxmail.org>:
> Hi,
>
> I'm looking for some guide to install TomEE with JAVA8.as per the
> documentation [1] JAVA8 supports "TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384"
> cipher suits.
>
> Can someone suggest me a document or how to?
>
> [1]
> http://docs.oracle.com/javase/8/docs/technotes/guides/security/SunProviders.html#importlimits
>
>
> Regards,
> San
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4670165.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>
Re: Java 8 and possible TomEE 1.7.0
Posted by san <sa...@linuxmail.org>.
Hi,
I'm looking for some guide to install TomEE with JAVA8.as per the
documentation [1] JAVA8 supports "TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384"
cipher suits.
Can someone suggest me a document or how to?
[1]http://docs.oracle.com/javase/8/docs/technotes/guides/security/SunProviders.html#importlimits
Regards,
San
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4670165.html
Sent from the TomEE Dev mailing list archive at Nabble.com.
Re: Java 8 and possible TomEE 1.7.0
Posted by m1000 <ma...@gmail.com>.
Perfect !
--
View this message in context: http://openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4668802.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Java 8 and possible TomEE 1.7.0
Posted by Romain Manni-Bucau <rm...@gmail.com>.
the patch is attached to the jira, we are just waiting/helping openjpa
to fully support it but I use it with the patch applied locally under
j8 since few days but with few jpa feature in the apps.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-04-14 22:12 GMT+02:00 m1000 <ma...@gmail.com>:
> Hi, So what version/build can run Java 8 applications ? Did 1.7.0 started ?
>
>
>
>
> --
> View this message in context: http://openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4668781.html
> Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Java 8 and possible TomEE 1.7.0
Posted by m1000 <ma...@gmail.com>.
Hi, So what version/build can run Java 8 applications ? Did 1.7.0 started ?
--
View this message in context: http://openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4668781.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Java 8 and possible TomEE 1.7.0
Posted by og0815 <ol...@gg-net.de>.
Hi,
thanx. We will have a look into this. JPA is not the problem, most of
the time we use hibernate (and 4.3.x supports java 8)
As always, keep up the good work.
Olli
Am 05.04.2014 12:53, schrieb Romain Manni-Bucau [via OpenEJB]:
> Actually this patch https://issues.apache.org/jira/browse/TOMEE-1167
> makes it working so you can test. Only issues are in openjpa and cxf
> which should upgrade too (patch submitted)
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
>
> 2014-04-05 12:15 GMT+02:00 og0815 <[hidden email]
> </user/SendEmail.jtp?type=node&node=4668603&i=0>>:
>
> > Hi,
> >
> > great to see that tomee is moving in the Java 8 direction. Waiting
> for this
> > since the first prereleases of JDK 8.
> > Any point on the website or the issue tracker to see the progress on
> this ?
> > Any thing I can do to help ?
> >
> > Regards,
> > Olli
> >
> >
> >
> > --
> > View this message in context:
> http://openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4668602.html
> > Sent from the OpenEJB Dev mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------
> If you reply to this email, your message will be added to the
> discussion below:
> http://openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4668603.html
>
> To unsubscribe from Java 8 and possible TomEE 1.7.0, click here
> <http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4668490&code=b2xpdmVyLmd1ZW50aGVyQGdnLW5ldC5kZXw0NjY4NDkwfDcyOTQ5NDMxOA==>.
> NAML
> <http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
GG-Net GmbH
Manhagener Allee 7
22926 Ahrensburg
Impressum gemäss § 35a GmbHG:
GG-Net GmbH - Sitz: Ahrensburg
Handelsregister: AG Lübeck HRB 7309 HL
Steuernummer: 30 293 57243
Geschäftsführer: Oliver Günther (M.Sc.), Anja Günther
--
View this message in context: http://openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4668626.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Java 8 and possible TomEE 1.7.0
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Actually this patch https://issues.apache.org/jira/browse/TOMEE-1167
makes it working so you can test. Only issues are in openjpa and cxf
which should upgrade too (patch submitted)
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-04-05 12:15 GMT+02:00 og0815 <ol...@gg-net.de>:
> Hi,
>
> great to see that tomee is moving in the Java 8 direction. Waiting for this
> since the first prereleases of JDK 8.
> Any point on the website or the issue tracker to see the progress on this ?
> Any thing I can do to help ?
>
> Regards,
> Olli
>
>
>
> --
> View this message in context: http://openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4668602.html
> Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Java 8 and possible TomEE 1.7.0
Posted by og0815 <ol...@gg-net.de>.
Hi,
great to see that tomee is moving in the Java 8 direction. Waiting for this
since the first prereleases of JDK 8.
Any point on the website or the issue tracker to see the progress on this ?
Any thing I can do to help ?
Regards,
Olli
--
View this message in context: http://openejb.979440.n4.nabble.com/Java-8-and-possible-TomEE-1-7-0-tp4668490p4668602.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Java 8 and possible TomEE 1.7.0
Posted by helio frota <00...@gmail.com>.
Great !
o/
-------------------------------------------
http://eprogramming.github.io
On Tue, Apr 1, 2014 at 6:48 AM, Romain Manni-Bucau <rm...@gmail.com>wrote:
> happy and just able to work since soon java 8 will be the default for
> some enterprises cause of security constraints so we need it and we
> are on the way to get it :)
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
>
> 2014-04-01 11:46 GMT+02:00 Thiago Veronezi <th...@veronezi.org>:
> > +1 for java 1.7
> > +10 for java 1.8
> >
> > Java 1.8 would be perfect. Even if we won't implement Java EE 8 in any
> time
> > soon, using Java 8 in Java AA applications would make some happy users.
> :)
> >
> > []s,
> > Thiago.
> >
> >
> >
> > On Tue, Apr 1, 2014 at 2:36 AM, Romain Manni-Bucau <
> rmannibucau@gmail.com>wrote:
> >
> >> 1. -> dont see any major features actually, which ones are you thiking
> >> about? (just to make it clear)
> >> Romain Manni-Bucau
> >> Twitter: @rmannibucau
> >> Blog: http://rmannibucau.wordpress.com/
> >> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> >> Github: https://github.com/rmannibucau
> >>
> >>
> >>
> >> 2014-04-01 8:06 GMT+02:00 Jean-Louis MONTEIRO <je...@gmail.com>:
> >> > I would say +1 for 1.7.0 in any case.
> >> > And I would do in 2 steps:
> >> >
> >> > 1. release the trunk as it's today. Very stable and a huge amount of
> >> fixes
> >> > and some important refactoring and add ons. Requires a 1.7.0 by itself
> >> and
> >> > not only a 1.6.1.
> >> > 2. upgrade to asm5 during the next 2 weeks and gather as many
> feedback as
> >> > possible on 1.7.0. We can then just push a 1.8.0
> >> >
> >> > Right after that, we can focus on 2.0 to support java ee 7 on a new
> >> branch.
> >> > And stay with 1.x on release maintenance stage.
> >> >
> >> > We could at least maintain 1.7 and 1.! cause the code base is almost
> the
> >> > same. Only all deps (openjpa, owb, xbean, etc) changed to support
> java 8.
> >> >
> >> >
> >> >
> >> > 2014-04-01 7:02 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
> >> >
> >> >> Id say +1...when well get asm5 (in progress see next lines). So just
> >> wait
> >> >> few days and we upgrade once we support it to say consistent.
> >> >>
> >> >> About asm xbean vote is in progress, owb is using the snapshot but
> >> already
> >> >> java5, openjpa has a patch for it and just wait it to be applied and
> our
> >> >> code will be updated pretty quickly so just need time.
> >> >> Le 1 avr. 2014 04:03, "David Blevins" <da...@gmail.com> a
> >> écrit :
> >> >>
> >> >> > Romain had pinged me offline about the idea of upgrading our ASM
> >> >> > dependencies to v5 so we could support Java 8 (code compiled in
> Java 8
> >> >> > can't be read by ASM v4 or earlier).
> >> >> >
> >> >> > This combined with the Mojarra and EclipseLink / Plume distribution
> >> seem
> >> >> > like good features for a 1.7.0
> >> >> >
> >> >> > We also have the quartz repackaging we did which are not quite
> "minor"
> >> >> > patch changes.
> >> >> >
> >> >> > Any thoughts on updating the trunk version to 1.7?
> >> >> >
> >> >> >
> >> >> > -David
> >> >> >
> >> >> >
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Jean-Louis
> >>
>
Re: Java 8 and possible TomEE 1.7.0
Posted by Romain Manni-Bucau <rm...@gmail.com>.
happy and just able to work since soon java 8 will be the default for
some enterprises cause of security constraints so we need it and we
are on the way to get it :)
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-04-01 11:46 GMT+02:00 Thiago Veronezi <th...@veronezi.org>:
> +1 for java 1.7
> +10 for java 1.8
>
> Java 1.8 would be perfect. Even if we won't implement Java EE 8 in any time
> soon, using Java 8 in Java AA applications would make some happy users. :)
>
> []s,
> Thiago.
>
>
>
> On Tue, Apr 1, 2014 at 2:36 AM, Romain Manni-Bucau <rm...@gmail.com>wrote:
>
>> 1. -> dont see any major features actually, which ones are you thiking
>> about? (just to make it clear)
>> Romain Manni-Bucau
>> Twitter: @rmannibucau
>> Blog: http://rmannibucau.wordpress.com/
>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> Github: https://github.com/rmannibucau
>>
>>
>>
>> 2014-04-01 8:06 GMT+02:00 Jean-Louis MONTEIRO <je...@gmail.com>:
>> > I would say +1 for 1.7.0 in any case.
>> > And I would do in 2 steps:
>> >
>> > 1. release the trunk as it's today. Very stable and a huge amount of
>> fixes
>> > and some important refactoring and add ons. Requires a 1.7.0 by itself
>> and
>> > not only a 1.6.1.
>> > 2. upgrade to asm5 during the next 2 weeks and gather as many feedback as
>> > possible on 1.7.0. We can then just push a 1.8.0
>> >
>> > Right after that, we can focus on 2.0 to support java ee 7 on a new
>> branch.
>> > And stay with 1.x on release maintenance stage.
>> >
>> > We could at least maintain 1.7 and 1.! cause the code base is almost the
>> > same. Only all deps (openjpa, owb, xbean, etc) changed to support java 8.
>> >
>> >
>> >
>> > 2014-04-01 7:02 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
>> >
>> >> Id say +1...when well get asm5 (in progress see next lines). So just
>> wait
>> >> few days and we upgrade once we support it to say consistent.
>> >>
>> >> About asm xbean vote is in progress, owb is using the snapshot but
>> already
>> >> java5, openjpa has a patch for it and just wait it to be applied and our
>> >> code will be updated pretty quickly so just need time.
>> >> Le 1 avr. 2014 04:03, "David Blevins" <da...@gmail.com> a
>> écrit :
>> >>
>> >> > Romain had pinged me offline about the idea of upgrading our ASM
>> >> > dependencies to v5 so we could support Java 8 (code compiled in Java 8
>> >> > can't be read by ASM v4 or earlier).
>> >> >
>> >> > This combined with the Mojarra and EclipseLink / Plume distribution
>> seem
>> >> > like good features for a 1.7.0
>> >> >
>> >> > We also have the quartz repackaging we did which are not quite "minor"
>> >> > patch changes.
>> >> >
>> >> > Any thoughts on updating the trunk version to 1.7?
>> >> >
>> >> >
>> >> > -David
>> >> >
>> >> >
>> >>
>> >
>> >
>> >
>> > --
>> > Jean-Louis
>>
Re: Java 8 and possible TomEE 1.7.0
Posted by Thiago Veronezi <th...@veronezi.org>.
+1 for java 1.7
+10 for java 1.8
Java 1.8 would be perfect. Even if we won't implement Java EE 8 in any time
soon, using Java 8 in Java AA applications would make some happy users. :)
[]s,
Thiago.
On Tue, Apr 1, 2014 at 2:36 AM, Romain Manni-Bucau <rm...@gmail.com>wrote:
> 1. -> dont see any major features actually, which ones are you thiking
> about? (just to make it clear)
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
>
> 2014-04-01 8:06 GMT+02:00 Jean-Louis MONTEIRO <je...@gmail.com>:
> > I would say +1 for 1.7.0 in any case.
> > And I would do in 2 steps:
> >
> > 1. release the trunk as it's today. Very stable and a huge amount of
> fixes
> > and some important refactoring and add ons. Requires a 1.7.0 by itself
> and
> > not only a 1.6.1.
> > 2. upgrade to asm5 during the next 2 weeks and gather as many feedback as
> > possible on 1.7.0. We can then just push a 1.8.0
> >
> > Right after that, we can focus on 2.0 to support java ee 7 on a new
> branch.
> > And stay with 1.x on release maintenance stage.
> >
> > We could at least maintain 1.7 and 1.! cause the code base is almost the
> > same. Only all deps (openjpa, owb, xbean, etc) changed to support java 8.
> >
> >
> >
> > 2014-04-01 7:02 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
> >
> >> Id say +1...when well get asm5 (in progress see next lines). So just
> wait
> >> few days and we upgrade once we support it to say consistent.
> >>
> >> About asm xbean vote is in progress, owb is using the snapshot but
> already
> >> java5, openjpa has a patch for it and just wait it to be applied and our
> >> code will be updated pretty quickly so just need time.
> >> Le 1 avr. 2014 04:03, "David Blevins" <da...@gmail.com> a
> écrit :
> >>
> >> > Romain had pinged me offline about the idea of upgrading our ASM
> >> > dependencies to v5 so we could support Java 8 (code compiled in Java 8
> >> > can't be read by ASM v4 or earlier).
> >> >
> >> > This combined with the Mojarra and EclipseLink / Plume distribution
> seem
> >> > like good features for a 1.7.0
> >> >
> >> > We also have the quartz repackaging we did which are not quite "minor"
> >> > patch changes.
> >> >
> >> > Any thoughts on updating the trunk version to 1.7?
> >> >
> >> >
> >> > -David
> >> >
> >> >
> >>
> >
> >
> >
> > --
> > Jean-Louis
>
Re: Java 8 and possible TomEE 1.7.0
Posted by Romain Manni-Bucau <rm...@gmail.com>.
1. -> dont see any major features actually, which ones are you thiking
about? (just to make it clear)
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-04-01 8:06 GMT+02:00 Jean-Louis MONTEIRO <je...@gmail.com>:
> I would say +1 for 1.7.0 in any case.
> And I would do in 2 steps:
>
> 1. release the trunk as it's today. Very stable and a huge amount of fixes
> and some important refactoring and add ons. Requires a 1.7.0 by itself and
> not only a 1.6.1.
> 2. upgrade to asm5 during the next 2 weeks and gather as many feedback as
> possible on 1.7.0. We can then just push a 1.8.0
>
> Right after that, we can focus on 2.0 to support java ee 7 on a new branch.
> And stay with 1.x on release maintenance stage.
>
> We could at least maintain 1.7 and 1.! cause the code base is almost the
> same. Only all deps (openjpa, owb, xbean, etc) changed to support java 8.
>
>
>
> 2014-04-01 7:02 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
>
>> Id say +1...when well get asm5 (in progress see next lines). So just wait
>> few days and we upgrade once we support it to say consistent.
>>
>> About asm xbean vote is in progress, owb is using the snapshot but already
>> java5, openjpa has a patch for it and just wait it to be applied and our
>> code will be updated pretty quickly so just need time.
>> Le 1 avr. 2014 04:03, "David Blevins" <da...@gmail.com> a écrit :
>>
>> > Romain had pinged me offline about the idea of upgrading our ASM
>> > dependencies to v5 so we could support Java 8 (code compiled in Java 8
>> > can't be read by ASM v4 or earlier).
>> >
>> > This combined with the Mojarra and EclipseLink / Plume distribution seem
>> > like good features for a 1.7.0
>> >
>> > We also have the quartz repackaging we did which are not quite "minor"
>> > patch changes.
>> >
>> > Any thoughts on updating the trunk version to 1.7?
>> >
>> >
>> > -David
>> >
>> >
>>
>
>
>
> --
> Jean-Louis
Re: Java 8 and possible TomEE 1.7.0
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
I would say +1 for 1.7.0 in any case.
And I would do in 2 steps:
1. release the trunk as it's today. Very stable and a huge amount of fixes
and some important refactoring and add ons. Requires a 1.7.0 by itself and
not only a 1.6.1.
2. upgrade to asm5 during the next 2 weeks and gather as many feedback as
possible on 1.7.0. We can then just push a 1.8.0
Right after that, we can focus on 2.0 to support java ee 7 on a new branch.
And stay with 1.x on release maintenance stage.
We could at least maintain 1.7 and 1.! cause the code base is almost the
same. Only all deps (openjpa, owb, xbean, etc) changed to support java 8.
2014-04-01 7:02 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
> Id say +1...when well get asm5 (in progress see next lines). So just wait
> few days and we upgrade once we support it to say consistent.
>
> About asm xbean vote is in progress, owb is using the snapshot but already
> java5, openjpa has a patch for it and just wait it to be applied and our
> code will be updated pretty quickly so just need time.
> Le 1 avr. 2014 04:03, "David Blevins" <da...@gmail.com> a écrit :
>
> > Romain had pinged me offline about the idea of upgrading our ASM
> > dependencies to v5 so we could support Java 8 (code compiled in Java 8
> > can't be read by ASM v4 or earlier).
> >
> > This combined with the Mojarra and EclipseLink / Plume distribution seem
> > like good features for a 1.7.0
> >
> > We also have the quartz repackaging we did which are not quite "minor"
> > patch changes.
> >
> > Any thoughts on updating the trunk version to 1.7?
> >
> >
> > -David
> >
> >
>
--
Jean-Louis
Re: Java 8 and possible TomEE 1.7.0
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Id say +1...when well get asm5 (in progress see next lines). So just wait
few days and we upgrade once we support it to say consistent.
About asm xbean vote is in progress, owb is using the snapshot but already
java5, openjpa has a patch for it and just wait it to be applied and our
code will be updated pretty quickly so just need time.
Le 1 avr. 2014 04:03, "David Blevins" <da...@gmail.com> a écrit :
> Romain had pinged me offline about the idea of upgrading our ASM
> dependencies to v5 so we could support Java 8 (code compiled in Java 8
> can't be read by ASM v4 or earlier).
>
> This combined with the Mojarra and EclipseLink / Plume distribution seem
> like good features for a 1.7.0
>
> We also have the quartz repackaging we did which are not quite "minor"
> patch changes.
>
> Any thoughts on updating the trunk version to 1.7?
>
>
> -David
>
>