Fixed in 1.7.x and trunk
https://issues.apache.org/jira/browse/TOMEE-1391
org.apache.maven.plugins
maven-remote-resources-plugin
1.5
org.apache.maven.shared
maven-filtering
1
add it as dependency of the remote resources plugin (think this is the one):
.
here
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 :
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
org.apache.maven.shared
maven-filtering
1.2
after placing the dependency configuration it download the 1.2 ve
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-
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
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.
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 :
> Ok Thanks
>
>
> On Wed, Jun 25,
Ok Thanks
On Wed, Jun 25, 2014 at 6:03 PM, Romain Manni-Bucau
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.word
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/rma
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.LifecycleExecutionExceptio
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 :
> I tried to compile TomEE w
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
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 Man
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
--
Vi
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/rman
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#importl
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.
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.l
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.
.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:/
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/r
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.n
Great !
o/
---
http://eprogramming.github.io
On Tue, Apr 1, 2014 at 6:48 AM, Romain Manni-Bucau 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
> a
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
Gith
+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 wrote:
> 1. -> dont see any major features ac
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
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 fee
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 u
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
29 matches
Mail list logo
