That should answer to every questions: http://search.maven.org/#browse%7C-427252420
I'm going to update the maven reference to the dependency. Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin :http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 26 October 2011 02:44, sebb <seb...@gmail.com> wrote: > That's better, but it's still a problem to depend on Java 1.6 given > that OGNL targets 1.5. > > The simplest solution is to remove the automatic benchmarks profile > activation code, i.e. delete the activation section. > > It is still possible to run the benchmark by enabling the benchmarks > profile, but at least automated builds should run without further > configuration. > > It would be better to move the code to a separate module. > Running it once creates files that interfere with subsequent test runs > that don't use the benchmarks profile. > Or someone needs to fix it so that the benchmarks profile does not > mess up the test classes. > > On 26 October 2011 01:22, Maurizio Cucchiara <mcucchi...@apache.org> wrote: >> They said tomorrow >> https://groups.google.com/group/junit-benchmarks/msg/4dd978765cabfce6?hl=it >> >> >> Twitter :http://www.twitter.com/m_cucchiara >> G+ :https://plus.google.com/107903711540963855921 >> Linkedin :http://www.linkedin.com/in/mauriziocucchiara >> >> Maurizio Cucchiara >> >> >> >> On 26 October 2011 02:10, sebb <seb...@gmail.com> wrote: >>> On 26 October 2011 00:54, Maurizio Cucchiara <mcucchi...@apache.org> wrote: >>>>> 2. ask to JB team if there is a specific reason. >>>> And just for the record the JB team doesn't plan to support java 5. >>> >>> Any idea when they plan to release 3.0? >>> >>>> Twitter :http://www.twitter.com/m_cucchiara >>>> G+ :https://plus.google.com/107903711540963855921 >>>> Linkedin :http://www.linkedin.com/in/mauriziocucchiara >>>> >>>> Maurizio Cucchiara >>>> >>>> >>>> >>>> On 25 October 2011 13:01, Maurizio Cucchiara <mcucchi...@apache.org> wrote: >>>>> Simo, >>>>> I am afraid that junit-benchmark was compiled with java 6, so >>>>> basically we have 2 options: >>>>> 1. change jdk settings on Jenkins (but I'm totally against it) >>>>> 3. (that it was I'm currently trying to do) change build command on >>>>> Jenkins in order to exclude benchmark profile >>>>> >>>>> Twitter :http://www.twitter.com/m_cucchiara >>>>> G+ :https://plus.google.com/107903711540963855921 >>>>> Linkedin :http://www.linkedin.com/in/mauriziocucchiara >>>>> >>>>> Maurizio Cucchiara >>>>> >>>>> >>>>> >>>>> On 25 October 2011 12:09, Simone Tripodi <simonetrip...@apache.org> wrote: >>>>>> Hi all guys, >>>>>> looks like there is a problem that cannot be managed by our side >>>>>> >>>>>> [INFO] ------------------------------------------------------------- >>>>>> [ERROR] COMPILATION ERROR : >>>>>> [INFO] ------------------------------------------------------------- >>>>>> [ERROR] >>>>>> /home/jenkins/jenkins-slave/workspace/ognl/src/benchmarks/java/org/apache/commons/ognl/performance/BasePerformanceTest.java:[24,-1] >>>>>> cannot access com.carrotsearch.junitbenchmarks.BenchmarkOptions >>>>>> bad class file: >>>>>> /home/jenkins/.m2/repository/com/carrotsearch/junit-benchmarks/0.3.0-SNAPSHOT/junit-benchmarks-0.3.0-SNAPSHOT.jar(com/carrotsearch/junitbenchmarks/BenchmarkOptions.class) >>>>>> class file has wrong version 50.0, should be 49.0 >>>>>> >>>>>> Maybe Olivier can help? >>>>>> Thanks a lot in advance! >>>>>> Simo >>>>>> >>>>>> http://people.apache.org/~simonetripodi/ >>>>>> http://simonetripodi.livejournal.com/ >>>>>> http://twitter.com/simonetripodi >>>>>> http://www.99soft.org/ >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ---------- Forwarded message ---------- >>>>>> From: Apache Jenkins Server <jenk...@builds.apache.org> >>>>>> Date: Tue, Oct 25, 2011 at 11:59 AM >>>>>> Subject: ognl - Build # 153 - Failure >>>>>> To: simone.trip...@gmail.com >>>>>> >>>>>> >>>>>> The Apache Jenkins build system has built ognl (build #153) >>>>>> >>>>>> Status: Failure >>>>>> >>>>>> Check console output at https://builds.apache.org/job/ognl/153/ to >>>>>> view the results. >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>>>> >>>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> For additional commands, e-mail: dev-h...@commons.apache.org >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org