You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@buildr.apache.org by Antoine Toulme <an...@lunar-ocean.com> on 2010/06/05 20:30:19 UTC
ScalaSpecs jdk6 only ?
Guys,
I'm seeing this error when running specs with jdk5:
Exception in thread "main" java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
at
org.apache.buildr.SpecsSingletonRunner.run(SpecsSingletonRunner.java:54)
at
org.apache.buildr.SpecsSingletonRunner.main(SpecsSingletonRunner.java:35)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at
org.apache.buildr.SpecsSingletonRunner.run(SpecsSingletonRunner.java:52)
... 1 more
Caused by: java.lang.NoSuchMethodError: java.lang.String.isEmpty()Z
at
org.specs.runner.OutputReporter$class.reportSpec(ConsoleReporter.scala:91)
at org.specs.Specification.reportSpec(Specification.scala:43)
at
org.specs.runner.OutputReporter$$anonfun$report$1.apply(ConsoleReporter.scala:73)
at
org.specs.runner.OutputReporter$$anonfun$report$1.apply(ConsoleReporter.scala:73)
at scala.List.foreach(List.scala:841)
at
org.specs.runner.OutputReporter$class.report(ConsoleReporter.scala:73)
at org.specs.Specification.report(Specification.scala:43)
at
org.specs.runner.OutputReporter$class.report(ConsoleReporter.scala:64)
at org.specs.Specification.report(Specification.scala:43)
at org.specs.Specification.report(Specification.scala:43)
at org.specs.runner.Reporter$class.reportSpecs(Reporter.scala:192)
at org.specs.Specification...
I got the sources here:
http://specs.googlecode.com/svn/trunk/src/main/scala/org/specs/runner/ConsoleReporter.scala
Does this mean ScalaSpecs is jdk6 only ?
Can it be fixed somehow ? or do we officially let go of jdk5 compatibility ?
Thanks,
Antoine
Re: ScalaSpecs jdk6 only ?
Posted by Alex Boisvert <al...@gmail.com>.
Yeah, let's wait to build that bridge until someone actually wants to cross it.
Alex
On Sunday, June 6, 2010, Daniel Spiewak <dj...@gmail.com> wrote:
> The only other option would be to ask Eric for a custom build of Specs, and
> that seems...excessive. I don't think we should throw out all attempts to
> run Specs under Java 5, but a warning would certainly be appropriate. If
> people *really* need the functionality, then we should allow it, but they
> should be warned that they need a custom build to do it.
>
> Daniel
>
> On Sun, Jun 6, 2010 at 11:00 AM, Antoine Toulme <an...@lunar-ocean.com>wrote:
>
>> Giving it some thought while doing house work yesterday, I'm thinking those
>> specs should only run with a jdk6.
>>
>> I'll put a condition around the Scala Specs specs.
>>
>> On Sat, Jun 5, 2010 at 11:50, Antoine Toulme <antoine@lunar-ocean.com
>> >wrote:
>>
>> > After some enquiry over IRC (where apparently mentioning jdk5 makes you
>> > look like a retard :) ),
>> >
>> > I got a reference to this issue on ScalaSpecs:
>> > http://code.google.com/p/specs/issues/detail?id=140
>> >
>> > The last comment mentions that isEmpty is implemented as part of
>> RichString
>> > on Scala for jdk5, and so I was told the problem would go away if we used
>> a
>> > compiled version of ScalaSpecs that used a target compatibility of 1.5.
>> >
>> > Before I take it further, do we have objections ?
>> >
>> > On Sat, Jun 5, 2010 at 11:30, Antoine Toulme <antoine@lunar-ocean.com
>> >wrote:
>> >
>> >> Guys,
>> >>
>> >> I'm seeing this error when running specs with jdk5:
>> >>
>> >> Exception in thread "main" java.lang.RuntimeException:
>> >> java.lang.reflect.InvocationTargetException
>> >> at
>> >> org.apache.buildr.SpecsSingletonRunner.run(SpecsSingletonRunner.java:54)
>> >> at
>> >>
>> org.apache.buildr.SpecsSingletonRunner.main(SpecsSingletonRunner.java:35)
>> >> Caused by: java.lang.reflect.InvocationTargetException
>> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >> at
>> >>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> >> at
>> >>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> >> at java.lang.reflect.Method.invoke(Method.java:592)
>> >> at
>> >> org.apache.buildr.SpecsSingletonRunner.run(SpecsSingletonRunner.java:52)
>> >> ... 1 more
>> >> Caused by: java.lang.NoSuchMethodError: java.lang.String.isEmpty()Z
>> >> at
>> >>
>> org.specs.runner.OutputReporter$class.reportSpec(ConsoleReporter.scala:91)
>> >> at org.specs.Specification.reportSpec(Specification.scala:43)
>> >> at
>> >>
>> org.specs.runner.OutputReporter$$anonfun$report$1.apply(ConsoleReporter.scala:73)
>> >> at
>> >>
>> org.specs.runner.OutputReporter$$anonfun$report$1.apply(ConsoleReporter.scala:73)
>> >> at scala.List.foreach(List.scala:841)
>> >> at
>> >> org.specs.runner.OutputReporter$class.report(ConsoleReporter.scala:73)
>> >> at org.specs.Specification.report(Specification.scala:43)
>> >> at
>> >> org.specs.runner.OutputReporter$class.report(ConsoleReporter.scala:64)
>> >> at org.specs.Specification.report(Specification.scala:43)
>> >> at org.specs.Specification.report(Specification.scala:43)
>> >> at
>> org.specs.runner.Reporter$class.reportSpecs(Reporter.scala:192)
>> >> at org.specs.Specification...
>> >>
>> >> I got the sources here:
>> >>
>> >>
>> http://specs.googlecode.com/svn/trunk/src/main/scala/org/specs/runner/ConsoleReporter.scala
>> >>
>> >> Does this mean ScalaSpecs is jdk6 only ?
>> >>
>> >> Can it be f
Re: ScalaSpecs jdk6 only ?
Posted by Daniel Spiewak <dj...@gmail.com>.
The only other option would be to ask Eric for a custom build of Specs, and
that seems...excessive. I don't think we should throw out all attempts to
run Specs under Java 5, but a warning would certainly be appropriate. If
people *really* need the functionality, then we should allow it, but they
should be warned that they need a custom build to do it.
Daniel
On Sun, Jun 6, 2010 at 11:00 AM, Antoine Toulme <an...@lunar-ocean.com>wrote:
> Giving it some thought while doing house work yesterday, I'm thinking those
> specs should only run with a jdk6.
>
> I'll put a condition around the Scala Specs specs.
>
> On Sat, Jun 5, 2010 at 11:50, Antoine Toulme <antoine@lunar-ocean.com
> >wrote:
>
> > After some enquiry over IRC (where apparently mentioning jdk5 makes you
> > look like a retard :) ),
> >
> > I got a reference to this issue on ScalaSpecs:
> > http://code.google.com/p/specs/issues/detail?id=140
> >
> > The last comment mentions that isEmpty is implemented as part of
> RichString
> > on Scala for jdk5, and so I was told the problem would go away if we used
> a
> > compiled version of ScalaSpecs that used a target compatibility of 1.5.
> >
> > Before I take it further, do we have objections ?
> >
> > On Sat, Jun 5, 2010 at 11:30, Antoine Toulme <antoine@lunar-ocean.com
> >wrote:
> >
> >> Guys,
> >>
> >> I'm seeing this error when running specs with jdk5:
> >>
> >> Exception in thread "main" java.lang.RuntimeException:
> >> java.lang.reflect.InvocationTargetException
> >> at
> >> org.apache.buildr.SpecsSingletonRunner.run(SpecsSingletonRunner.java:54)
> >> at
> >>
> org.apache.buildr.SpecsSingletonRunner.main(SpecsSingletonRunner.java:35)
> >> Caused by: java.lang.reflect.InvocationTargetException
> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> at
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >> at
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >> at java.lang.reflect.Method.invoke(Method.java:592)
> >> at
> >> org.apache.buildr.SpecsSingletonRunner.run(SpecsSingletonRunner.java:52)
> >> ... 1 more
> >> Caused by: java.lang.NoSuchMethodError: java.lang.String.isEmpty()Z
> >> at
> >>
> org.specs.runner.OutputReporter$class.reportSpec(ConsoleReporter.scala:91)
> >> at org.specs.Specification.reportSpec(Specification.scala:43)
> >> at
> >>
> org.specs.runner.OutputReporter$$anonfun$report$1.apply(ConsoleReporter.scala:73)
> >> at
> >>
> org.specs.runner.OutputReporter$$anonfun$report$1.apply(ConsoleReporter.scala:73)
> >> at scala.List.foreach(List.scala:841)
> >> at
> >> org.specs.runner.OutputReporter$class.report(ConsoleReporter.scala:73)
> >> at org.specs.Specification.report(Specification.scala:43)
> >> at
> >> org.specs.runner.OutputReporter$class.report(ConsoleReporter.scala:64)
> >> at org.specs.Specification.report(Specification.scala:43)
> >> at org.specs.Specification.report(Specification.scala:43)
> >> at
> org.specs.runner.Reporter$class.reportSpecs(Reporter.scala:192)
> >> at org.specs.Specification...
> >>
> >> I got the sources here:
> >>
> >>
> http://specs.googlecode.com/svn/trunk/src/main/scala/org/specs/runner/ConsoleReporter.scala
> >>
> >> Does this mean ScalaSpecs is jdk6 only ?
> >>
> >> Can it be fixed somehow ? or do we officially let go of jdk5
> compatibility
> >> ?
> >>
> >> Thanks,
> >>
> >> Antoine
> >>
> >
> >
>
Re: ScalaSpecs jdk6 only ?
Posted by Antoine Toulme <an...@lunar-ocean.com>.
Giving it some thought while doing house work yesterday, I'm thinking those
specs should only run with a jdk6.
I'll put a condition around the Scala Specs specs.
On Sat, Jun 5, 2010 at 11:50, Antoine Toulme <an...@lunar-ocean.com>wrote:
> After some enquiry over IRC (where apparently mentioning jdk5 makes you
> look like a retard :) ),
>
> I got a reference to this issue on ScalaSpecs:
> http://code.google.com/p/specs/issues/detail?id=140
>
> The last comment mentions that isEmpty is implemented as part of RichString
> on Scala for jdk5, and so I was told the problem would go away if we used a
> compiled version of ScalaSpecs that used a target compatibility of 1.5.
>
> Before I take it further, do we have objections ?
>
> On Sat, Jun 5, 2010 at 11:30, Antoine Toulme <an...@lunar-ocean.com>wrote:
>
>> Guys,
>>
>> I'm seeing this error when running specs with jdk5:
>>
>> Exception in thread "main" java.lang.RuntimeException:
>> java.lang.reflect.InvocationTargetException
>> at
>> org.apache.buildr.SpecsSingletonRunner.run(SpecsSingletonRunner.java:54)
>> at
>> org.apache.buildr.SpecsSingletonRunner.main(SpecsSingletonRunner.java:35)
>> Caused by: java.lang.reflect.InvocationTargetException
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:592)
>> at
>> org.apache.buildr.SpecsSingletonRunner.run(SpecsSingletonRunner.java:52)
>> ... 1 more
>> Caused by: java.lang.NoSuchMethodError: java.lang.String.isEmpty()Z
>> at
>> org.specs.runner.OutputReporter$class.reportSpec(ConsoleReporter.scala:91)
>> at org.specs.Specification.reportSpec(Specification.scala:43)
>> at
>> org.specs.runner.OutputReporter$$anonfun$report$1.apply(ConsoleReporter.scala:73)
>> at
>> org.specs.runner.OutputReporter$$anonfun$report$1.apply(ConsoleReporter.scala:73)
>> at scala.List.foreach(List.scala:841)
>> at
>> org.specs.runner.OutputReporter$class.report(ConsoleReporter.scala:73)
>> at org.specs.Specification.report(Specification.scala:43)
>> at
>> org.specs.runner.OutputReporter$class.report(ConsoleReporter.scala:64)
>> at org.specs.Specification.report(Specification.scala:43)
>> at org.specs.Specification.report(Specification.scala:43)
>> at org.specs.runner.Reporter$class.reportSpecs(Reporter.scala:192)
>> at org.specs.Specification...
>>
>> I got the sources here:
>>
>> http://specs.googlecode.com/svn/trunk/src/main/scala/org/specs/runner/ConsoleReporter.scala
>>
>> Does this mean ScalaSpecs is jdk6 only ?
>>
>> Can it be fixed somehow ? or do we officially let go of jdk5 compatibility
>> ?
>>
>> Thanks,
>>
>> Antoine
>>
>
>
Re: ScalaSpecs jdk6 only ?
Posted by Antoine Toulme <an...@lunar-ocean.com>.
After some enquiry over IRC (where apparently mentioning jdk5 makes you look
like a retard :) ),
I got a reference to this issue on ScalaSpecs:
http://code.google.com/p/specs/issues/detail?id=140
The last comment mentions that isEmpty is implemented as part of RichString
on Scala for jdk5, and so I was told the problem would go away if we used a
compiled version of ScalaSpecs that used a target compatibility of 1.5.
Before I take it further, do we have objections ?
On Sat, Jun 5, 2010 at 11:30, Antoine Toulme <an...@lunar-ocean.com>wrote:
> Guys,
>
> I'm seeing this error when running specs with jdk5:
>
> Exception in thread "main" java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.buildr.SpecsSingletonRunner.run(SpecsSingletonRunner.java:54)
> at
> org.apache.buildr.SpecsSingletonRunner.main(SpecsSingletonRunner.java:35)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:592)
> at
> org.apache.buildr.SpecsSingletonRunner.run(SpecsSingletonRunner.java:52)
> ... 1 more
> Caused by: java.lang.NoSuchMethodError: java.lang.String.isEmpty()Z
> at
> org.specs.runner.OutputReporter$class.reportSpec(ConsoleReporter.scala:91)
> at org.specs.Specification.reportSpec(Specification.scala:43)
> at
> org.specs.runner.OutputReporter$$anonfun$report$1.apply(ConsoleReporter.scala:73)
> at
> org.specs.runner.OutputReporter$$anonfun$report$1.apply(ConsoleReporter.scala:73)
> at scala.List.foreach(List.scala:841)
> at
> org.specs.runner.OutputReporter$class.report(ConsoleReporter.scala:73)
> at org.specs.Specification.report(Specification.scala:43)
> at
> org.specs.runner.OutputReporter$class.report(ConsoleReporter.scala:64)
> at org.specs.Specification.report(Specification.scala:43)
> at org.specs.Specification.report(Specification.scala:43)
> at org.specs.runner.Reporter$class.reportSpecs(Reporter.scala:192)
> at org.specs.Specification...
>
> I got the sources here:
>
> http://specs.googlecode.com/svn/trunk/src/main/scala/org/specs/runner/ConsoleReporter.scala
>
> Does this mean ScalaSpecs is jdk6 only ?
>
> Can it be fixed somehow ? or do we officially let go of jdk5 compatibility
> ?
>
> Thanks,
>
> Antoine
>