Nabble - Scala - Tools

Re: [scala-tools] Scala plugin for Netbeans 6.8beta - BoxedBooleanArray class not found

2009-11-26T07:59:05Z

Oh, yeah, just verified on NetBeans 6.8 beta, the new Scala nightly
built broke it. So. please use Scala-2.8.0-BetaRC1 before I release a
new version (will for NetBeans 6.8RC1)

On Thu, Nov 26, 2009 at 11:50 PM, Caoyuan <dcaoyuan@...> wrote:

> On Thu, Nov 26, 2009 at 11:38 PM, Louis Botterill
> <chillipower.uk@...> wrote:
>> Hi, is that the very latest nightly? not much different to
>> scala-2.8.0.r19853 though?
>>
>> I'll recheck with that version. What OS and Netbeans, 6.8beta?
>
> Mime: OSX 10.5.8, NetBeans RC1 (to be released in days). But NetBeans
> 6.8beta and corresponding scala plugin you downloaded according to
> http://wiki.netbeans.org/Scala68v1 should work too.
>
> If there is still issues, please report me, and I'll try to release
> new plugin as soon as possible.
>
> Cheers,
> -Caoyuan
>
>> I'm OSX 10.6.2 and Netbeans 6.8beta - not found a version of Scala for which
>> this will work yet, so if I can get a working combination I will be very
>> happy!
>>
>> cheers,
>>
>> Louis
>>
>>
>> 2009/11/26 Caoyuan <dcaoyuan@...>
>>>
>>> Just did a quick test upon 2.8.0.r19896, seems no problem.
>>>
>>> On Thu, Nov 26, 2009 at 6:04 PM, Caoyuan <dcaoyuan@...> wrote:
>>> > On Thu, Nov 26, 2009 at 5:56 PM, Louis Botterill
>>> > <chillipower.uk@...> wrote:
>>> >> Hi,
>>> >>
>>> >> Also, actually just looking at your stack trace - did your JVM
>>> >> environment
>>> >> run out of memory (heap) during the build?
>>> >
>>> > It's not so plain problem, the heap size is already very large.
>>> >
>>> > Cheers,
>>> > -Caoyuan
>>> >
>>> >
>>> >>
>>> >> cheers,
>>> >>
>>> >> Louis
>>> >>
>>> >>
>>> >> 2009/11/26 Caoyuan <dcaoyuan@...>
>>> >>>
>>> >>> Per the information, it maybe caused by Scala-2.8.0.r19853 itself? I
>>> >>> can not build Scala upon current trunk due to:
>>> >>> [scaladoc]
>>> >>> /Users/dcaoyuan/myprjs/scala/scala/src/library/scala/Console.scala:88:
>>> >>> warning: Tag '@param@' is not recognised
>>> >>> [scaladoc] def setOut(out: OutputStream): Unit =
>>> >>> [scaladoc] ^
>>> >>> [scaladoc] java.lang.OutOfMemoryError: Java heap space
>>> >>> [scaladoc] at java.util.Arrays.copyOfRange(Arrays.java:3209)
>>> >>> [scaladoc] at java.lang.String.<init>(String.java:215)
>>> >>> [scaladoc] at
>>> >>>
>>> >>> scala.collection.mutable.StringBuilder.toString(StringBuilder.scala:844)
>>> >>> [scaladoc] at scala.xml.XML$.write(XML.scala:103)
>>> >>> [scaladoc] at scala.xml.XML$$anonfun$save$2.apply(XML.scala:86)
>>> >>> [scaladoc] at scala.xml.XML$$anonfun$save$2.apply(XML.scala:86)
>>> >>> [scaladoc] at
>>> >>> scala.util.control.Exception$Catch.apply(Exception.scala:79)
>>> >>> [scaladoc] at scala.xml.XML$.save(XML.scala:85)
>>> >>> [scaladoc] at
>>> >>> scala.tools.nsc.doc.html.HtmlPage.writeFor(HtmlPage.scala:55)
>>> >>> [scaladoc] at
>>> >>>
>>> >>> scala.tools.nsc.doc.html.SiteFactory.writeTemplate$1(SiteFactory.scala:70)
>>> >>> [scaladoc] at
>>> >>>
>>> >>>
>>> >>> scala.tools.nsc.doc.html.SiteFactory$$anonfun$writeTemplate$1$2.apply(SiteFactory.scala:72)
>>> >>> [scaladoc] at
>>> >>>
>>> >>>
>>> >>> scala.tools.nsc.doc.html.SiteFactory$$anonfun$writeTemplate$1$2.apply(SiteFactory.scala:72)
>>> >>> [scaladoc] at
>>> >>>
>>> >>>
>>> >>> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:159)
>>> >>> [scaladoc] at
>>> >>>
>>> >>>
>>> >>> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:159)
>>> >>> [scaladoc] at
>>> >>> scala.collection.LinearSeqLike$class.foreach(LinearSeqLike.scala:88)
>>> >>> [scaladoc] at
>>> >>> scala.collection.immutable.List.foreach(List.scala:29)
>>> >>> [scaladoc] at
>>> >>> scala.collection.TraversableLike$class.map(TraversableLike.scala:159)
>>> >>> [scaladoc] at scala.collection.immutable.List.map(List.scala:29)
>>> >>> [scaladoc] at
>>> >>>
>>> >>> scala.tools.nsc.doc.html.SiteFactory.writeTemplate$1(SiteFactory.scala:72)
>>> >>> [scaladoc] at
>>> >>>
>>> >>>
>>> >>> scala.tools.nsc.doc.html.SiteFactory$$anonfun$writeTemplate$1$2.apply(SiteFactory.scala:72)
>>> >>> [scaladoc] at
>>> >>>
>>> >>>
>>> >>> scala.tools.nsc.doc.html.SiteFactory$$anonfun$writeTemplate$1$2.apply(SiteFactory.scala:72)
>>> >>> [scaladoc] at
>>> >>>
>>> >>>
>>> >>> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:159)
>>> >>> [scaladoc] at
>>> >>>
>>> >>>
>>> >>> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:159)
>>> >>> [scaladoc] at
>>> >>> scala.collection.LinearSeqLike$class.foreach(LinearSeqLike.scala:88)
>>> >>> [scaladoc] at
>>> >>> scala.collection.immutable.List.foreach(List.scala:29)
>>> >>> [scaladoc] at
>>> >>> scala.collection.TraversableLike$class.map(TraversableLike.scala:159)
>>> >>> [scaladoc] at scala.collection.immutable.List.map(List.scala:29)
>>> >>> [scaladoc] at
>>> >>>
>>> >>> scala.tools.nsc.doc.html.SiteFactory.writeTemplate$1(SiteFactory.scala:72)
>>> >>> [scaladoc] at
>>> >>>
>>> >>>
>>> >>> scala.tools.nsc.doc.html.SiteFactory$$anonfun$writeTemplate$1$2.apply(SiteFactory.scala:72)
>>> >>> [scaladoc] at
>>> >>>
>>> >>>
>>> >>> scala.tools.nsc.doc.html.SiteFactory$$anonfun$writeTemplate$1$2.apply(SiteFactory.scala:72)
>>> >>> [scaladoc] at
>>> >>>
>>> >>>
>>> >>> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:159)
>>> >>> [scaladoc] at
>>> >>>
>>> >>>
>>> >>> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:159)
>>> >>>
>>> >>> So, I did not test it upon recent Scala nightly version yet. Or I will
>>> >>> try to build a new Scala version, or, would you please try it on
>>> >>> Scala-2.8.0betaRC2?
>>> >>>
>>> >>> Thanks.
>>> >>>
>>> >>> -Caoyuan
>>> >>>
>>> >>>
>>> >>> On Thu, Nov 26, 2009 at 4:07 PM, Louis Botterill
>>> >>> <chillipower.uk@...> wrote:
>>> >>> > Hi,
>>> >>> >
>>> >>> > Thanks for the reply, settings are:
>>> >>> >
>>> >>> >
>>> >>> >
>>> >>> > SCALA_HOME=/Users/chillipower_uk/dev/tools/scala/scala-2.8.0.r19853-b20091125020156
>>> >>> >
>>> >>> > Which was the latest nightly build from 25th-Nov-2009
>>> >>> >
>>> >>> > javac 1.6.0_15
>>> >>> >
>>> >>> > OS is OSX Snow Leopard (10.6.2)
>>> >>> >
>>> >>> > Syntax colouring - yes works fine. It appears to be partially
>>> >>> > working,
>>> >>> > in
>>> >>> > that I can create a new Scala project, create classes/objects etc
>>> >>> > and
>>> >>> > syntax
>>> >>> > highlighting is there.
>>> >>> >
>>> >>> > However, just noticed another similar problem, it crashes on code
>>> >>> > completion
>>> >>> > too:
>>> >>> >
>>> >>> > scala.tools.nsc.FatalError: object BoxesRunTime does not have a
>>> >>> > member
>>> >>> > equals
>>> >>> >     at
>>> >>> >
>>> >>> >
>>> >>> > scala.tools.nsc.symtab.Definitions$definitions$.getMember(Definitions.scala:435)
>>> >>> >     at
>>> >>> >
>>> >>> >
>>> >>> > scala.tools.nsc.backend.icode.GenICode$ICodePhase.<init>(GenICode.scala:59)
>>> >>> >     at
>>> >>> > scala.tools.nsc.backend.icode.GenICode.newPhase(GenICode.scala:39)
>>> >>> >     at
>>> >>> > scala.tools.nsc.backend.icode.GenICode.newPhase(GenICode.scala:24)
>>> >>> >     at scala.tools.nsc.Global$Run$$anonfun$5.apply(Global.scala:693)
>>> >>> >     at scala.tools.nsc.Global$Run$$anonfun$5.apply(Global.scala:692)
>>> >>> >     at
>>> >>> > scala.collection.LinearSeqLike$class.foreach(LinearSeqLike.scala:84)
>>> >>> >     at scala.collection.immutable.List.foreach(List.scala:29)
>>> >>> >     at scala.tools.nsc.Global$Run.<init>(Global.scala:692)
>>> >>> >     at
>>> >>> >
>>> >>> >
>>> >>> > org.netbeans.modules.scala.core.interactive.Global$TyperRun.<init>(Global.scala:590)
>>> >>> >     at
>>> >>> >
>>> >>> >
>>> >>> > org.netbeans.modules.scala.core.interactive.Global.reloadSources(Global.scala:297)
>>> >>> >     at
>>> >>> >
>>> >>> >
>>> >>> > org.netbeans.modules.scala.core.interactive.Global.typedTreeAt(Global.scala:317)
>>> >>> >     at
>>> >>> >
>>> >>> >
>>> >>> > org.netbeans.modules.scala.core.interactive.Global.typeMembers(Global.scala:413)
>>> >>> >     at
>>> >>> >
>>> >>> >
>>> >>> > org.netbeans.modules.scala.core.interactive.Global$$anonfun$getTypeCompletion$1.apply(Global.scala:408)
>>> >>> >     at
>>> >>> >
>>> >>> >
>>> >>> > org.netbeans.modules.scala.core.interactive.Global$$anonfun$getTypeCompletion$1.apply(Global.scala:408)
>>> >>> >     at
>>> >>> >
>>> >>> >
>>> >>> > org.netbeans.modules.scala.core.interactive.Global.respond(Global.scala:284)
>>> >>> >     at
>>> >>> >
>>> >>> >
>>> >>> > org.netbeans.modules.scala.core.interactive.Global.getTypeCompletion(Global.scala:408)
>>> >>> >     at
>>> >>> >
>>> >>> >
>>> >>> > org.netbeans.modules.scala.core.interactive.CompilerControl$$anon$2.apply(CompilerControl.scala:105)
>>> >>> >     at
>>> >>> >
>>> >>> >
>>> >>> > org.netbeans.modules.scala.core.interactive.CompilerControl$$anon$2.apply(CompilerControl.scala:104)
>>> >>> >     at
>>> >>> >
>>> >>> >
>>> >>> > org.netbeans.modules.scala.core.interactive.Global.pollForWork(Global.scala:133)
>>> >>> > [catch] at
>>> >>> >
>>> >>> >
>>> >>> > org.netbeans.modules.scala.core.interactive.Global$$anon$2.run(Global.scala:194)
>>> >>> >
>>> >>> >
>>> >>> > which maybe is related?
>>> >>> >
>>> >>> > thanks, Louis
>>> >>> >
>>> >>> >
>>> >>> > 2009/11/26 Caoyuan <dcaoyuan@...>
>>> >>> >>
>>> >>> >> Hi,
>>> >>> >>
>>> >>> >> What's your SCALA_HOME setting? Can you see the syntax highlighting
>>> >>> >> on
>>> >>> >> editor window? Your os?
>>> >>> >>
>>> >>> >> On Thu, Nov 26, 2009 at 5:16 AM, Louis Botterill
>>> >>> >> <chillipower.uk@...> wrote:
>>> >>> >> > Hi,
>>> >>> >> >
>>> >>> >> > Using latest Netbeans 6.8beta and latest nightly build of Scala
>>> >>> >> > (25th
>>> >>> >> > Nov
>>> >>> >> > 2009), a new Scala project with just one valid test class fails
>>> >>> >> > to
>>> >>> >> > compile
>>> >>> >> > with a class scala.runtime.BoxedBooleanArray class not found
>>> >>> >> > error,
>>> >>> >> > the
>>> >>> >> > full
>>> >>> >> > details are below.
>>> >>> >> >
>>> >>> >> > I thought this might be useful as potentially easy to fix and get
>>> >>> >> > Scala
>>> >>> >> > plugin for Netbeans 6.8 working again?
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > Created dir:
>>> >>> >> >
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > /Users/chillipower_uk/dev/projects/testprojects/training/scala-training/build/classes
>>> >>> >> > Compiling 1 source file to
>>> >>> >> >
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > /Users/chillipower_uk/dev/projects/testprojects/training/scala-training/build/classes
>>> >>> >> > error: fatal error: class scala.runtime.BoxedBooleanArray not
>>> >>> >> > found.
>>> >>> >> > one error found
>>> >>> >> >
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > /Users/chillipower_uk/dev/projects/testprojects/training/scala-training/nbproject/build-impl.xml:229:
>>> >>> >> > Compile failed; see the compiler error output for details.
>>> >>> >> >         at scala.tools.ant.Scalac.error(Scalac.scala:461)
>>> >>> >> >         at
>>> >>> >> > scala.tools.ant.FastScalac.execute(FastScalac.scala:103)
>>> >>> >> >         at
>>> >>> >> >
>>> >>> >> > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
>>> >>> >> >         at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown
>>> >>> >> > Source)
>>> >>> >> >         at
>>> >>> >> >
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> >>> >> >         at java.lang.reflect.Method.invoke(Method.java:597)
>>> >>> >> >         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.taskdefs.Sequential.execute(Sequential.java:62)
>>> >>> >> >         at
>>> >>> >> >
>>> >>> >> > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
>>> >>> >> >         at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown
>>> >>> >> > Source)
>>> >>> >> >         at
>>> >>> >> >
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> >>> >> >         at java.lang.reflect.Method.invoke(Method.java:597)
>>> >>> >> >         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.taskdefs.MacroInstance.execute(MacroInstance.java:394)
>>> >>> >> >         at
>>> >>> >> >
>>> >>> >> > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
>>> >>> >> >         at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown
>>> >>> >> > Source)
>>> >>> >> >         at
>>> >>> >> >
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> >>> >> >         at java.lang.reflect.Method.invoke(Method.java:597)
>>> >>> >> >         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:357)
>>> >>> >> >         at
>>> >>> >> > org.apache.tools.ant.Target.performTasks(Target.java:385)
>>> >>> >> >         at
>>> >>> >> >
>>> >>> >> > org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
>>> >>> >> >         at
>>> >>> >> > org.apache.tools.ant.Project.executeTarget(Project.java:1306)
>>> >>> >> >         at
>>> >>> >> >
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>>> >>> >> >         at
>>> >>> >> > org.apache.tools.ant.Project.executeTargets(Project.java:1189)
>>> >>> >> >         at
>>> >>> >> >
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:278)
>>> >>> >> >         at
>>> >>> >> >
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:498)
>>> >>> >> >         at
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
>>> >>> >> >
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > /Users/chillipower_uk/dev/projects/testprojects/training/scala-training/nbproject/build-impl.xml:405:
>>> >>> >> > The following error occurred while executing this line:
>>> >>> >> >
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > /Users/chillipower_uk/dev/projects/testprojects/training/scala-training/nbproject/build-impl.xml:229:
>>> >>> >> > Compile failed because of an internal compiler error (Compile
>>> >>> >> > failed;
>>> >>> >> > see
>>> >>> >> > the compiler error output for details.); see the error output for
>>> >>> >> > details.
>>> >>> >> > BUILD FAILED (total time: 1 second)
>>> >>> >> >
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > --
>>> >>> >> > www.chillipower.com
>>> >>> >> > http://louisbotterill.blogspot.com/
>>> >>> >> >
>>> >>> >> > Please consider your environmental responsibility before printing
>>> >>> >> > this
>>> >>> >> > e-mail
>>> >>> >> >
>>> >>> >> >
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > --
>>> >>> >> > www.chillipower.com
>>> >>> >> > http://louisbotterill.blogspot.com/
>>> >>> >> >
>>> >>> >> > Please consider your environmental responsibility before printing
>>> >>> >> > this
>>> >>> >> > e-mail
>>> >>> >> >
>>> >>> >> >
>>> >>> >
>>> >>> >
>>> >>> >
>>> >>> > --
>>> >>> > www.chillipower.com
>>> >>> > http://louisbotterill.blogspot.com/
>>> >>> >
>>> >>> > Please consider your environmental responsibility before printing
>>> >>> > this
>>> >>> > e-mail
>>> >>> >
>>> >>> >
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> www.chillipower.com
>>> >> http://louisbotterill.blogspot.com/
>>> >>
>>> >> Please consider your environmental responsibility before printing this
>>> >> e-mail
>>> >>
>>> >>
>>> >
>>
>>
>>
>> --
>> www.chillipower.com
>> http://louisbotterill.blogspot.com/
>>
>> Please consider your environmental responsibility before printing this
>> e-mail
>>
>>
>

Re: [scala-tools] Scala plugin for Netbeans 6.8beta - BoxedBooleanArray class not found

2009-11-25T22:27:22Z

Hi,

What's your SCALA_HOME setting? Can you see the syntax highlighting on
editor window? Your os?

On Thu, Nov 26, 2009 at 5:16 AM, Louis Botterill
<chillipower.uk@...> wrote:

> Hi,
>
> Using latest Netbeans 6.8beta and latest nightly build of Scala (25th Nov
> 2009), a new Scala project with just one valid test class fails to compile
> with a class scala.runtime.BoxedBooleanArray class not found error, the full
> details are below.
>
> I thought this might be useful as potentially easy to fix and get Scala
> plugin for Netbeans 6.8 working again?
>
>
> Created dir:
> /Users/chillipower_uk/dev/projects/testprojects/training/scala-training/build/classes
> Compiling 1 source file to
> /Users/chillipower_uk/dev/projects/testprojects/training/scala-training/build/classes
> error: fatal error: class scala.runtime.BoxedBooleanArray not found.
> one error found
> /Users/chillipower_uk/dev/projects/testprojects/training/scala-training/nbproject/build-impl.xml:229:
> Compile failed; see the compiler error output for details.
>         at scala.tools.ant.Scalac.error(Scalac.scala:461)
>         at scala.tools.ant.FastScalac.execute(FastScalac.scala:103)
>         at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
>         at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         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.taskdefs.Sequential.execute(Sequential.java:62)
>         at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
>         at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         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.taskdefs.MacroInstance.execute(MacroInstance.java:394)
>         at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
>         at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         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:357)
>         at org.apache.tools.ant.Target.performTasks(Target.java:385)
>         at
> org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
>         at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
>         at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>         at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
>         at
> org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:278)
>         at
> org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:498)
>         at
> org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
> /Users/chillipower_uk/dev/projects/testprojects/training/scala-training/nbproject/build-impl.xml:405:
> The following error occurred while executing this line:
> /Users/chillipower_uk/dev/projects/testprojects/training/scala-training/nbproject/build-impl.xml:229:
> Compile failed because of an internal compiler error (Compile failed; see
> the compiler error output for details.); see the error output for details.
> BUILD FAILED (total time: 1 second)
>
>
>
> --
> www.chillipower.com
> http://louisbotterill.blogspot.com/
>
> Please consider your environmental responsibility before printing this
> e-mail
>
>
>
>
> --
> www.chillipower.com
> http://louisbotterill.blogspot.com/
>
> Please consider your environmental responsibility before printing this
> e-mail
>
>

[scala-tools] Scala plugin for Netbeans 6.8beta - BoxedBooleanArray class not found

2009-11-25T13:16:46Z

Hi,

Using latest Netbeans 6.8beta and latest nightly build of Scala (25th Nov 2009), a new Scala project with just one valid test class fails to compile with a class scala.runtime.BoxedBooleanArray class not found error, the full details are below.

I thought this might be useful as potentially easy to fix and get Scala plugin for Netbeans 6.8 working again?

Created dir: /Users/chillipower_uk/dev/projects/testprojects/training/scala-training/build/classes
Compiling 1 source file to /Users/chillipower_uk/dev/projects/testprojects/training/scala-training/build/classes
error: fatal error: class scala.runtime.BoxedBooleanArray not found.
one error found
/Users/chillipower_uk/dev/projects/testprojects/training/scala-training/nbproject/build-impl.xml:229: Compile failed; see the compiler error output for details.
        at scala.tools.ant.Scalac.error(Scalac.scala:461)
        at scala.tools.ant.FastScalac.execute(FastScalac.scala:103)
        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
        at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        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.taskdefs.Sequential.execute(Sequential.java:62)
        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
        at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        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.taskdefs.MacroInstance.execute(MacroInstance.java:394)
        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
        at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        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:357)
        at org.apache.tools.ant.Target.performTasks(Target.java:385)
        at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
        at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
        at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
        at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
        at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:278)
        at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:498)
        at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
/Users/chillipower_uk/dev/projects/testprojects/training/scala-training/nbproject/build-impl.xml:405: The following error occurred while executing this line:
/Users/chillipower_uk/dev/projects/testprojects/training/scala-training/nbproject/build-impl.xml:229: Compile failed because of an internal compiler error (Compile failed; see the compiler error output for details.); see the error output for details.
BUILD FAILED (total time: 1 second)

--
www.chillipower.com
http://louisbotterill.blogspot.com/

Please consider your environmental responsibility before printing this e-mail

--
www.chillipower.com
http://louisbotterill.blogspot.com/

Please consider your environmental responsibility before printing this e-mail

Re: [scala-tools] [NetBeans] How to I diagnose lack of compilation

2009-11-25T00:57:09Z

On Wed, Nov 18, 2009 at 3:15 PM, David Pollak
<feeder.of.the.bears@...> wrote:

>
>
> On Tue, Nov 17, 2009 at 6:47 PM, Caoyuan <dcaoyuan@...> wrote:
>>
>> Hi,
>>
>> On Wed, Nov 18, 2009 at 7:40 AM, David Pollak
>> <feeder.of.the.bears@...> wrote:
>> > Howdy,
>> >
>> > I installed NetBeans on a new system and for some reason, it no longer
>> > compiles code while I'm typing (I don't get real time compilation
>> > errors).
>> >
>> > How do I diagnose this issue?
>>
>>
>> If it's a Mac OS, and $SCALA_HOME is setting. the you may wan to take a
>> look at:
>> http://wiki.netbeans.org/MacOSXEnvForApp
>>
>
> Setting SCALA_HOME doesn't improve the situation for editing Lift sources.
>
> Lift is a Maven-based project and I'm wondering if there's something about
> the pom.xml files that is not triggering the appropriate compilation. How
> can I debug that?

I just caught it: I should explicit set -extdirs <dirs> to empty in
NetBeans scalac settings, otherwise all jars under ${scala.home}/lib
will be added automatically (as default).

I fixed it in NetBeans 6.8 plugin, will release a new version for
NetBeans 6.8RC1 in couple of days.

-Caoyuan

>
>>
>> >
>> > Thanks,
>> >
>> > David
>> >
>> > PS -- I'm using NB 6.7.1 with the most recent 6.7 plugin
>> > PPS -- I'm currently using Scala 2.7.7, if I use NB 6.8 with the newer
>> > plugin, what version of Scala will it use?
>>
>> All nightly version recently and 2.8.0-betaRC1 should work.
>> http://wiki.netbeans.org/Scala68v1
>>
>> -Caoyuan
>>
>> >
>> > --
>> > Lift, the simply functional web framework http://liftweb.net
>> > Beginning Scala http://www.apress.com/book/view/1430219890
>> > Follow me: http://twitter.com/dpp
>> > Surf the harmonics
>> >
>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Surf the harmonics
>

[scala-tools] [ANN] YaScalaDT 0.1.0 (eclipse plugin)

2009-11-25T00:40:54Z

Hi,

As some my coworkers, some of you could interested by the first version of my first eclipse plugin ;). There is no site/doc yet.
Current feature :
* very basic editor (comment, string, keyword highlight)
* error marker from console output
* hyperlink/jumper on error/warning from console output

The last 2 features are present in all my editor/configuration and is a must have for me.
Marker/Hyperlink support scala-maven-plugin output. So you could create an extranel tool who call scala:cc (or scala:compile) and have error updated in your project.
I've not test but marker/jumper should work with sbt, builr but you need to custom the command to emit (print to console) the line
<path>: -1: compiling
then every marker for <path> (could be the root source dir => recursive) are removed/reset

There is no configuration panel.

The EPFL Scala plugin is not required, and both could work together (from my coworker).

https://sourceforge.net/projects/alchim/files/YaScalaDT/0.1.0/net_alchim31_eclipse_yascaladt_0.1.0.200911202226.jar/download

feedback welcome. (I already work of the second version, more info near)

/davidB

Re: [scala-tools] Problem with maven-scala-plugin 2.13

2009-11-24T00:38:31Z

I forgot : my Apologies for troubles.

On Mon, Nov 23, 2009 at 22:16, David Bernard <david.bernard.31@...> wrote:

I deployed 2.13.1 that should fix the repository issue.

* good practices for "professional" team (to avoid breaking build due to externals resources):

** use an internal repository manager that proxy/cache external repository (who could failed,...) an to host internal artifact (to share between developers) like nexus, archiva, artifactory,...

** manage maven plugin like "regular" lib/dependency :
*** set the version explicitly
*** only release with non SNAPSHOT (like checked by mvn release:prepare)
*** upgrade and check locally before sharing with other developer

* scala-tools.org like other repo can come and go (If you decide to stop to pay), go up and down like others (but less due to mirroring).

/davidB

PS: We use those pratice in my current team

On Mon, Nov 23, 2009 at 17:46, David Pollak <feeder.of.the.bears@...> wrote:

I think it's seriously suboptimal to include references to repos other than the main maven repo and the scala-tools.org repo. Repos come and go. Repos go up and down. Depending on things that may not be there in the future or may not be there on any given day is a whole lot less than good for teams that need to be able to build 24x7.

On Mon, Nov 23, 2009 at 6:02 AM, David Bernard <david.bernard.31@...> wrote:

It's seems that the repository of SnakeYAML is longer available at http://snakeyamlrepo.appspot.com/repository, but since a new version was push to central repo.
I'll push (later this evening) a version of maven-scala-plugin that use the version of central repo.

Thanks for using maven-scala-plugin (and reporting bugs, Sorry for them)

/davidB

On Mon, Nov 23, 2009 at 14:29, Mario Camou <mcamou@...> wrote:

Hi everyone,

I'm having a problem with maven-scala-plugin 2.13, it's looking for a
new artifact called SnakeYAML which it's not finding. FWIW we have our
own Nexus repository which acts as a proxy to all other repos that we
need. Any ideas?

Here's the output:

$ mvn clean install

[--- snip snip snip --- messages from the clean phase --- ]

Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository central (http://central)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository scala-tools.org (http://scala-tools.oDownloading:
http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository snakeyaml (http://snakeyamlrepo.appspot.com/repository)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository jboss.releases (http://repository.jboss.org/maven2)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository central (http://central)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/org/apache/commons/commons-exec/1.0.1/commons-exec-1.0.1.jar
48K downloaded (commons-exec-1.0.1.jar)
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository central (http://central)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository scala-tools.org (http://scala-tools.org/repo-releases)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository snakeyaml (http://snakeyamlrepo.appspot.com/repository)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository jboss.releases (http://repository.jboss.org/maven2)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository central (http://central)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) SnakeYAML:SnakeYAML:jar:1.3

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=SnakeYAML
-DartifactId=SnakeYAML -Dversion=1.3 -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=SnakeYAML
-DartifactId=SnakeYAML -Dversion=1.3 -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url
] -DrepositoryId=[id]

Path to dependency:
1) org.scala-tools:maven-scala-plugin:maven-plugin:2.13
2) SnakeYAML:SnakeYAML:jar:1.3

----------
1 required artifact is missing.

for artifact:
org.scala-tools:maven-scala-plugin:maven-plugin:2.13

from the specified remote repositories:
nexus-public-snapshots
(http://aedea.abstra:8081/nexus/content/groups/public-snapshots),
nexus (http://aedea.abstra:8081/nexus/content/groups/public)

[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 minutes 2 seconds
[INFO] Finished at: Mon Nov 23 14:26:04 CET 2009
[INFO] Final Memory: 33M/79M
rg/repo-releases)

Regards,
-Mario.

--
I want to change the world but they won't give me the source code.

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

Re: [scala-tools] "New Scala Interpreter" button, and scala console factory

2009-11-24T00:38:01Z

Thanks for the patch! Actually, the test way to submit patches is via
the Scala trac at

https://lampsvn.epfl.ch/trac/scala

That way it's made sure that somebody will take a look at it.

Cheers

-- Martin

On Tue, Nov 24, 2009 at 6:33 AM, David Taylor <dltaylor@...> wrote:

> For your consideration:
>
> Refactors the new interpreter action a little bit to abstract the launching
> code out, and also provides an IConsoleFactory implementation, so I could
> add a New Scala Console to the Console Factories dropdown menu in the
> Console View.
>
> David Taylor
> Carnegie Mellon University '11
> Computer Science / Information Systems
> 1570 17th Ave, San Francisco CA 94122
> 415.425.8722
>

[scala-tools] "New Scala Interpreter" button, and scala console factory

2009-11-23T21:33:23Z

For your consideration:

Refactors the new interpreter action a little bit to abstract the launching code out, and also provides an IConsoleFactory implementation, so I could add a New Scala Console to the Console Factories dropdown menu in the Console View.

David Taylor
Carnegie Mellon University '11
Computer Science / Information Systems
1570 17th Ave, San Francisco CA 94122
415.425.8722

[plugin.patch]

Index: src/scala/tools/eclipse/interpreter/Action.scala =================================================================== --- src/scala/tools/eclipse/interpreter/Action.scala (revision 19767) +++ src/scala/tools/eclipse/interpreter/Action.scala (working copy) @@ -29,38 +29,11 @@ val shell = new Shell MessageDialog.openInformation(shell, "Scala Development Tools", "Intepreter could not be created") } - import org.eclipse.jdt.launching.IJavaLaunchConfigurationConstants._ - import org.eclipse.debug.core.DebugPlugin - val manager = DebugPlugin.getDefault().getLaunchManager(); - val launchType = manager.getLaunchConfigurationType(SCALA_INTERPRETER_LAUNCH_ID); - val projectName = target.get.getJavaProject.getProject.getName - //Pull out the first interpreter configuration we can find for the project. - val configuration = manager.getLaunchConfigurations(launchType).filter({ config => - projectName.equals(config.getAttribute(ATTR_PROJECT_NAME, "")) - }).headOption - val workingCopy = configuration match { - case Some(config) => - config.getWorkingCopy - case None => - val newConfig = launchType.newInstance(null, projectName); - newConfig.setAttribute(ATTR_PROJECT_NAME, projectName); - //TODO - What else do we need to set on the properties for this to work... - newConfig - } + val project = target.get.getJavaProject.getProject - target match { - case Some(x : IPackageFragment) => - workingCopy.setAttribute(InterpreterLaunchConstants.PACKAGE_IMPORT, x.getElementName) - case Some(x : ITypeRoot) => - - case _ => //Ignore - } - - import org.eclipse.debug.ui.DebugUITools - import org.eclipse.debug.core.ILaunchManager - DebugUITools.launch(workingCopy, ILaunchManager.RUN_MODE) - + import scala.tools.eclipse.interpreter.Factory + Factory.openConsoleInProjectFromTarget(project, target) } override def selectionChanged(action: IAction, select: ISelection) = { Index: src/scala/tools/eclipse/interpreter/Factory.scala =================================================================== --- src/scala/tools/eclipse/interpreter/Factory.scala (revision 0) +++ src/scala/tools/eclipse/interpreter/Factory.scala (revision 0) @@ -0,0 +1,94 @@ +/* + * Copyright 2005-2009 LAMP/EPFL + * @author David Taylor + */ +// $Id$ + +package scala.tools.eclipse.interpreter +import org.eclipse.core.resources.IProject +import org.eclipse.jdt.core.IJavaElement +import org.eclipse.jdt.core.IPackageFragment +import org.eclipse.jdt.core.ITypeRoot + +import org.eclipse.ui.PlatformUI +import org.eclipse.ui.IFileEditorInput +import org.eclipse.jface.action.IAction +import org.eclipse.jface.dialogs.MessageDialog +import org.eclipse.swt.widgets.Shell +import org.eclipse.ui.console.IConsoleFactory + + +/** + * This is the factory defintion that supplies a scala interpreter facotry + */ +class Factory extends IConsoleFactory { + override def openConsole() = { + val p = Factory.getCurrentProject + + p match { + case Some(project: IProject) => + Factory.openConsoleInProject(project) + case None => + val shell = new Shell + MessageDialog.openInformation(shell, "Scala Development Tools", "Must have a currently opened Scala or Java Project") + } + } + +} + +object Factory { + val SCALA_INTERPRETER_LAUNCH_ID = "scala.interpreter" + + def openConsoleInProject(project: IProject) = { + openConsoleInProjectFromTarget(project, None) + } + + def openConsoleInProjectFromTarget(project: IProject, target: Option[IJavaElement]) = { + import org.eclipse.jdt.launching.IJavaLaunchConfigurationConstants._ + import org.eclipse.debug.core.DebugPlugin + val manager = DebugPlugin.getDefault().getLaunchManager(); + val launchType = manager.getLaunchConfigurationType(SCALA_INTERPRETER_LAUNCH_ID); + val projectName = project.getName + //Pull out the first interpreter configuration we can find for the project. + val configuration = manager.getLaunchConfigurations(launchType).filter({ config => + projectName.equals(config.getAttribute(ATTR_PROJECT_NAME, "")) + }).headOption + + val workingCopy = configuration match { + case Some(config) => + config.getWorkingCopy + case None => + val newConfig = launchType.newInstance(null, projectName); + newConfig.setAttribute(ATTR_PROJECT_NAME, projectName); + //TODO - What else do we need to set on the properties for this to work... + newConfig + } + + target match { + case Some(x : IPackageFragment) => + workingCopy.setAttribute(InterpreterLaunchConstants.PACKAGE_IMPORT, x.getElementName) + case Some(x : ITypeRoot) => + + case _ => //Ignore + } + + import org.eclipse.debug.ui.DebugUITools + import org.eclipse.debug.core.ILaunchManager + DebugUITools.launch(workingCopy, ILaunchManager.RUN_MODE) + } + + def getCurrentProject() = { + val editorPart = PlatformUI.getWorkbench.getActiveWorkbenchWindow().getActivePage().getActiveEditor(); + var current_project : Option[IProject] = None + + if(editorPart != null) { + val input = editorPart.getEditorInput().asInstanceOf[IFileEditorInput] + val file = input.getFile() + val project = file.getProject(); + if (project != null) { + current_project = Some(project) + } + } + current_project + } +} Index: plugin.xml =================================================================== --- plugin.xml (revision 19767) +++ plugin.xml (working copy) @@ -495,6 +495,14 @@ </extension> + <extension + point="org.eclipse.ui.console.consoleFactories"> + <consoleFactory + class="scala.tools.eclipse.interpreter.Factory" + icon="icons/full/etool16/scala_app.gif" + label="Scala Console"/> + </extension> + <extension point="org.eclipse.ui.console.consolePageParticipants"> <consolePageParticipant class="scala.tools.eclipse.interpreter.PageParticipant"

Re: [scala-tools] Error highlights in Eclipse Scala

2009-11-23T15:48:05Z

Hi Kevin,

I was also blaming myself :-)

then I was blaming Maven and when this problem became really painful I decided to track it down. The only project were I couldn't reproduce this bug is the project where I keep all the SDT bugs that I've submitted (this might be because the classes in that project are usually not connected with each other).

Kevin Wright-4 wrote:

Wow, very nicely summarized :)

I've been suffering with this one too, but blaming myself (there was a
certain compiler plugin involved...)

Good work that man!

Re: [scala-tools] Error highlights in Eclipse Scala

2009-11-23T15:37:17Z

Wow, very nicely summarized :)

I've been suffering with this one too, but blaming myself (there was a certain compiler plugin involved...)

Good work that man!

On Mon, Nov 23, 2009 at 11:27 PM, Miles Sabin <miles@...> wrote:

On Mon, Nov 23, 2009 at 11:22 PM, Spiros Tzavellas <sptz45@...> wrote:
>
> I've already created bug 2689
> (https://lampsvn.epfl.ch/trac/scala/ticket/2689) that is probably related to
> this one. I'll try again sometime tomorrow.
>
> So far I've opened two bugs (2689 and 2680) while trying to find a small
> project that accurately reproduces this bug.

This is great stuff, BTW, very much appreciated ... expect some
progress in the next day or so.

Cheers,

Miles

--
Miles Sabin
tel: +44 (0)7813 944 528
skype: milessabin
http://www.chuusai.com/
http://twitter.com/milessabin

Re: [scala-tools] Error highlights in Eclipse Scala

2009-11-23T15:27:08Z

On Mon, Nov 23, 2009 at 11:22 PM, Spiros Tzavellas <sptz45@...> wrote:
>
> I've already created bug 2689
> (https://lampsvn.epfl.ch/trac/scala/ticket/2689) that is probably related to
> this one. I'll try again sometime tomorrow.
>
> So far I've opened two bugs (2689 and 2680) while trying to find a small
> project that accurately reproduces this bug.

This is great stuff, BTW, very much appreciated ... expect some
progress in the next day or so.

Cheers,

Miles

--
Miles Sabin
tel: +44 (0)7813 944 528
skype: milessabin
http://www.chuusai.com/
http://twitter.com/milessabin

Re: [scala-tools] Error highlights in Eclipse Scala

2009-11-23T15:22:34Z

I've already created bug 2689 (https://lampsvn.epfl.ch/trac/scala/ticket/2689) that is probably related to this one. I'll try again sometime tomorrow.

So far I've opened two bugs (2689 and 2680) while trying to find a small project that accurately reproduces this bug.

--
Spiros Tzavellas

Silvio Bierman wrote:

So it seems. Any chance you can reproduce this with only a couple of sample sources? I tried but to no avail...

Re: [scala-tools] Error highlights in Eclipse Scala

2009-11-23T14:51:24Z

Spiros Tzavellas wrote:

we are talking about the same bug.

So it seems. Any chance you can reproduce this with only a couple of sample sources? I tried but to no avail...

Re: [scala-tools] Error highlights in Eclipse Scala

2009-11-23T14:08:26Z

Hi Silvio,

we are talking about the same bug.

--
Spiros Tzavellas

Silvio Bierman wrote:

Well, I do not have any project dependencies. I build all code from other projects into a JAR per project and add those to the build path. I do have about 75 source files in the project.
Each clean/build makes this reappear. There are no errors in the code and as said by Spiros the code builds and runs fine.
The error highlights appear in any open source editor as soon as the clean happens. The subsequent build does not make them go away anymore. It seems like the editor picks up the deletion of the .class files but does not see them being recreated.

I can reproduce this at will but hardly consider it a small reproducible test case :-)

Regards,

Silvio

Re: [scala-tools] Problem with maven-scala-plugin 2.13

2009-11-23T13:16:40Z

I deployed 2.13.1 that should fix the repository issue.

* good practices for "professional" team (to avoid breaking build due to externals resources):

** use an internal repository manager that proxy/cache external repository (who could failed,...) an to host internal artifact (to share between developers) like nexus, archiva, artifactory,...

** manage maven plugin like "regular" lib/dependency :

*** set the version explicitly

*** only release with non SNAPSHOT (like checked by mvn release:prepare)

*** upgrade and check locally before sharing with other developer

* scala-tools.org like other repo can come and go (If you decide to stop to pay), go up and down like others (but less due to mirroring).

/davidB

PS: We use those pratice in my current team

On Mon, Nov 23, 2009 at 17:46, David Pollak <feeder.of.the.bears@...> wrote:

I think it's seriously suboptimal to include references to repos other than the main maven repo and the scala-tools.org repo. Repos come and go. Repos go up and down. Depending on things that may not be there in the future or may not be there on any given day is a whole lot less than good for teams that need to be able to build 24x7.

On Mon, Nov 23, 2009 at 6:02 AM, David Bernard <david.bernard.31@...> wrote:

It's seems that the repository of SnakeYAML is longer available at http://snakeyamlrepo.appspot.com/repository, but since a new version was push to central repo.
I'll push (later this evening) a version of maven-scala-plugin that use the version of central repo.

Thanks for using maven-scala-plugin (and reporting bugs, Sorry for them)

/davidB

On Mon, Nov 23, 2009 at 14:29, Mario Camou <mcamou@...> wrote:

Hi everyone,

I'm having a problem with maven-scala-plugin 2.13, it's looking for a
new artifact called SnakeYAML which it's not finding. FWIW we have our
own Nexus repository which acts as a proxy to all other repos that we
need. Any ideas?

Here's the output:

$ mvn clean install

[--- snip snip snip --- messages from the clean phase --- ]

Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository central (http://central)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository scala-tools.org (http://scala-tools.oDownloading:
http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository snakeyaml (http://snakeyamlrepo.appspot.com/repository)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository jboss.releases (http://repository.jboss.org/maven2)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository central (http://central)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/org/apache/commons/commons-exec/1.0.1/commons-exec-1.0.1.jar
48K downloaded (commons-exec-1.0.1.jar)
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository central (http://central)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository scala-tools.org (http://scala-tools.org/repo-releases)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository snakeyaml (http://snakeyamlrepo.appspot.com/repository)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository jboss.releases (http://repository.jboss.org/maven2)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository central (http://central)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) SnakeYAML:SnakeYAML:jar:1.3

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=SnakeYAML
-DartifactId=SnakeYAML -Dversion=1.3 -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=SnakeYAML
-DartifactId=SnakeYAML -Dversion=1.3 -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url
] -DrepositoryId=[id]

Path to dependency:
1) org.scala-tools:maven-scala-plugin:maven-plugin:2.13
2) SnakeYAML:SnakeYAML:jar:1.3

----------
1 required artifact is missing.

for artifact:
org.scala-tools:maven-scala-plugin:maven-plugin:2.13

from the specified remote repositories:
nexus-public-snapshots
(http://aedea.abstra:8081/nexus/content/groups/public-snapshots),
nexus (http://aedea.abstra:8081/nexus/content/groups/public)

[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 minutes 2 seconds
[INFO] Finished at: Mon Nov 23 14:26:04 CET 2009
[INFO] Final Memory: 33M/79M
rg/repo-releases)

Regards,
-Mario.

--
I want to change the world but they won't give me the source code.

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

[scala-tools] Exception in console - class scala.Array not found

2009-11-23T12:43:47Z

Hi,

Using fresh Eclipse - 3.5.1 with scala nightly
scala plugin -   2.8.0.r19784-b20091123033015
weaving service (enabled) -   1.6.4.20090313172428

Clean workspace with source of scala plugin and scala plugin aspects.

The problem is that syntax highlightning, outline and Hyperlinking is not working yelding the same error in the console.

I am not sure if this is problem of plugin or problem in my configuration. If you have some hints I will try it.

Thanks

I see following exception in the log:

Indexing document: /scala-plugin/src/scala/tools/eclipse/JVMUtils.scala
scala.tools.nsc.MissingRequirementError: class scala.Array not found.
    at scala.tools.nsc.symtab.Definitions$definitions$.getModuleOrClass(Definitions.scala:499)
    at scala.tools.nsc.symtab.Definitions$definitions$.getClass(Definitions.scala:457)
    at scala.tools.nsc.symtab.Definitions$definitions$.ArrayClass(Definitions.scala:212)
    at scala.tools.nsc.backend.icode.TypeKinds$REFERENCE.<init>(TypeKinds.scala:258)
    at scala.tools.nsc.backend.icode.GenICode$ICodePhase.<init>(GenICode.scala:53)
    at scala.tools.nsc.backend.icode.GenICode.newPhase(GenICode.scala:41)
    at scala.tools.nsc.backend.icode.GenICode.newPhase(GenICode.scala:25)
    at scala.tools.nsc.Global$Run$$anonfun$5.apply(Global.scala:657)
    at scala.tools.nsc.Global$Run$$anonfun$5.apply(Global.scala:656)
    at scala.collection.LinearSeqLike$class.foreach(LinearSeqLike.scala:85)
    at scala.collection.immutable.List.foreach(List.scala:29)
    at scala.tools.nsc.Global$Run.<init>(Global.scala:656)
    at scala.tools.nsc.interactive.Global$TyperRun.<init>(Global.scala:447)
    at scala.tools.nsc.interactive.Global.reloadSources(Global.scala:289)
    at scala.tools.nsc.interactive.Global.typedTree(Global.scala:319)
    at scala.tools.nsc.interactive.Global$$anonfun$getTypedTree$1.apply(Global.scala:331)
    at scala.tools.nsc.interactive.Global$$anonfun$getTypedTree$1.apply(Global.scala:331)
    at scala.tools.nsc.interactive.Global.respond(Global.scala:276)
    at scala.tools.nsc.interactive.Global.getTypedTree(Global.scala:331)
    at scala.tools.nsc.interactive.CompilerControl$$anon$3.apply(CompilerControl.scala:95)
    at scala.tools.nsc.interactive.CompilerControl$$anon$3.apply(CompilerControl.scala:94)
    at scala.tools.nsc.interactive.Global.pollForWork(Global.scala:132)
    at scala.tools.nsc.interactive.Global$$anon$2.run(Global.scala:192)

also there is another error:

org.eclipse.contribution.weaving.feature.group
scala.tools.nsc.MissingRequirementError: class scala.runtime.BooleanRef not found.

--
Peter Šiška
e-mail: siska.pe (at) gmail (dot) com
tel: +421 904 942 744

Re: [scala-tools] Error highlights in Eclipse Scala

2009-11-23T11:31:06Z

Well, I do not have any project dependencies. I build all code from other projects into a JAR per project and add those to the build path. I do have about 75 source files in the project.
Each clean/build makes this reappear. There are no errors in the code and as said by Spiros the code builds and runs fine.
The error highlights appear in any open source editor as soon as the clean happens. The subsequent build does not make them go away anymore. It seems like the editor picks up the deletion of the .class files but does not see them being recreated.

I can reproduce this at will but hardly consider it a small reproducible test case :-)

Regards,

Silvio

Re: [scala-tools] Problem with maven-scala-plugin 2.13

2009-11-23T08:46:20Z

I think it's seriously suboptimal to include references to repos other than the main maven repo and the scala-tools.org repo. Repos come and go. Repos go up and down. Depending on things that may not be there in the future or may not be there on any given day is a whole lot less than good for teams that need to be able to build 24x7.

On Mon, Nov 23, 2009 at 6:02 AM, David Bernard <david.bernard.31@...> wrote:

It's seems that the repository of SnakeYAML is longer available at http://snakeyamlrepo.appspot.com/repository, but since a new version was push to central repo.
I'll push (later this evening) a version of maven-scala-plugin that use the version of central repo.

Thanks for using maven-scala-plugin (and reporting bugs, Sorry for them)

/davidB

On Mon, Nov 23, 2009 at 14:29, Mario Camou <mcamou@...> wrote:

Hi everyone,

I'm having a problem with maven-scala-plugin 2.13, it's looking for a
new artifact called SnakeYAML which it's not finding. FWIW we have our
own Nexus repository which acts as a proxy to all other repos that we
need. Any ideas?

Here's the output:

$ mvn clean install

[--- snip snip snip --- messages from the clean phase --- ]

Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository central (http://central)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository scala-tools.org (http://scala-tools.oDownloading:
http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository snakeyaml (http://snakeyamlrepo.appspot.com/repository)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository jboss.releases (http://repository.jboss.org/maven2)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository central (http://central)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/org/apache/commons/commons-exec/1.0.1/commons-exec-1.0.1.jar
48K downloaded (commons-exec-1.0.1.jar)
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository central (http://central)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository scala-tools.org (http://scala-tools.org/repo-releases)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository snakeyaml (http://snakeyamlrepo.appspot.com/repository)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository jboss.releases (http://repository.jboss.org/maven2)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository central (http://central)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) SnakeYAML:SnakeYAML:jar:1.3

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=SnakeYAML
-DartifactId=SnakeYAML -Dversion=1.3 -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=SnakeYAML
-DartifactId=SnakeYAML -Dversion=1.3 -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url
] -DrepositoryId=[id]

Path to dependency:
1) org.scala-tools:maven-scala-plugin:maven-plugin:2.13
2) SnakeYAML:SnakeYAML:jar:1.3

----------
1 required artifact is missing.

for artifact:
org.scala-tools:maven-scala-plugin:maven-plugin:2.13

from the specified remote repositories:
nexus-public-snapshots
(http://aedea.abstra:8081/nexus/content/groups/public-snapshots),
nexus (http://aedea.abstra:8081/nexus/content/groups/public)

[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 minutes 2 seconds
[INFO] Finished at: Mon Nov 23 14:26:04 CET 2009
[INFO] Final Memory: 33M/79M
rg/repo-releases)

Regards,
-Mario.

--
I want to change the world but they won't give me the source code.

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

Re: [scala-tools] Error highlights in Eclipse Scala

2009-11-23T08:01:27Z

On Mon, Nov 23, 2009 at 3:28 PM, Spiros Tzavellas <sptz45@...> wrote:
> I've seen a similar problem in the 2.8 nightly build.
>
> When I do a clean followed by an automatic build I get lots of "not found
> type: ..." and "not found value: ..." error messages. The messages appear in
> the editor but not in the Problems View. The strange thing is that the code
> compiles and runs (all the junit test run without problems).

I've only seen this in complex scenarios with either multiple
dependent projects (symptom: spurious project-level errors) or where
early compilation failures have prevented otherwise good code from
being built which then has knock on effects on code which depends on
it (sounds like what you're experiencing).

As ever, if you're able to produce a small reproducible test case that
and attach it to a Trac ticket would be enormously helpful.

But yes, I agree, there are still issues with the new incremental
builder and presentation compiler ... moving them into scalac has
helped a lot but was never going to be a panacea.

Cheers,

Miles

--
Miles Sabin
tel: +44 (0)7813 944 528
skype: milessabin
http://www.chuusai.com/
http://twitter.com/milessabin

Re: [scala-tools] Error highlights in Eclipse Scala

2009-11-23T07:28:17Z

I've seen a similar problem in the 2.8 nightly build.

When I do a clean followed by an automatic build I get lots of "not found type: ..." and "not found value: ..." error messages. The messages appear in the editor but not in the Problems View. The strange thing is that the code compiles and runs (all the junit test run without problems).

--
Spiros Tzavellas

Silvio Bierman wrote:

In the 2.8 nightly build the Scala editor displays a lot of error highlights on sources that do not contain errors at all. All the import statements contain an error highlight saying "component is not a member of package xxx" and the the whole source is packed with highlights saying "not found: type xxx".
Sometimes closing the source and reopening it temporarily solves the problem but then they reappear is soon as I start editing.

Is this a known issue?

Gr. Silvio

Re: [scala-tools] Problem with maven-scala-plugin 2.13

2009-11-23T06:02:55Z

It's seems that the repository of SnakeYAML is longer available at http://snakeyamlrepo.appspot.com/repository, but since a new version was push to central repo.

I'll push (later this evening) a version of maven-scala-plugin that use the version of central repo.

Thanks for using maven-scala-plugin (and reporting bugs, Sorry for them)

/davidB

On Mon, Nov 23, 2009 at 14:29, Mario Camou <mcamou@...> wrote:

Hi everyone,

I'm having a problem with maven-scala-plugin 2.13, it's looking for a
new artifact called SnakeYAML which it's not finding. FWIW we have our
own Nexus repository which acts as a proxy to all other repos that we
need. Any ideas?

Here's the output:

$ mvn clean install

[--- snip snip snip --- messages from the clean phase --- ]

Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository central (http://central)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository scala-tools.org (http://scala-tools.oDownloading:
http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository snakeyaml (http://snakeyamlrepo.appspot.com/repository)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository jboss.releases (http://repository.jboss.org/maven2)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository central (http://central)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/org/apache/commons/commons-exec/1.0.1/commons-exec-1.0.1.jar
48K downloaded (commons-exec-1.0.1.jar)
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository central (http://central)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository scala-tools.org (http://scala-tools.org/repo-releases)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository snakeyaml (http://snakeyamlrepo.appspot.com/repository)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository jboss.releases (http://repository.jboss.org/maven2)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository central (http://central)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) SnakeYAML:SnakeYAML:jar:1.3

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=SnakeYAML
-DartifactId=SnakeYAML -Dversion=1.3 -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=SnakeYAML
-DartifactId=SnakeYAML -Dversion=1.3 -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url
] -DrepositoryId=[id]

Path to dependency:
1) org.scala-tools:maven-scala-plugin:maven-plugin:2.13
2) SnakeYAML:SnakeYAML:jar:1.3

----------
1 required artifact is missing.

for artifact:
org.scala-tools:maven-scala-plugin:maven-plugin:2.13

from the specified remote repositories:
nexus-public-snapshots
(http://aedea.abstra:8081/nexus/content/groups/public-snapshots),
nexus (http://aedea.abstra:8081/nexus/content/groups/public)

[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 minutes 2 seconds
[INFO] Finished at: Mon Nov 23 14:26:04 CET 2009
[INFO] Final Memory: 33M/79M
rg/repo-releases)

Regards,
-Mario.

--
I want to change the world but they won't give me the source code.

[scala-tools] Problem with maven-scala-plugin 2.13

2009-11-23T05:29:42Z

Hi everyone,

I'm having a problem with maven-scala-plugin 2.13, it's looking for a
new artifact called SnakeYAML which it's not finding. FWIW we have our
own Nexus repository which acts as a proxy to all other repos that we
need. Any ideas?

Here's the output:

$ mvn clean install

[--- snip snip snip --- messages from the clean phase --- ]

Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository central (http://central)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository scala-tools.org (http://scala-tools.oDownloading:
http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository snakeyaml (http://snakeyamlrepo.appspot.com/repository)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository jboss.releases (http://repository.jboss.org/maven2)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.pom
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:pom:1.3' in
repository central (http://central)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/org/apache/commons/commons-exec/1.0.1/commons-exec-1.0.1.jar
48K downloaded (commons-exec-1.0.1.jar)
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository central (http://central)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository scala-tools.org (http://scala-tools.org/repo-releases)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository snakeyaml (http://snakeyamlrepo.appspot.com/repository)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository jboss.releases (http://repository.jboss.org/maven2)
Downloading: http://aedea.abstra:8081/nexus/content/groups/public/SnakeYAML/SnakeYAML/1.3/SnakeYAML-1.3.jar
[INFO] Unable to find resource 'SnakeYAML:SnakeYAML:jar:1.3' in
repository central (http://central)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) SnakeYAML:SnakeYAML:jar:1.3

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=SnakeYAML
-DartifactId=SnakeYAML -Dversion=1.3 -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=SnakeYAML
-DartifactId=SnakeYAML -Dversion=1.3 -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url
] -DrepositoryId=[id]

Path to dependency:
1) org.scala-tools:maven-scala-plugin:maven-plugin:2.13
2) SnakeYAML:SnakeYAML:jar:1.3

----------
1 required artifact is missing.

for artifact:
org.scala-tools:maven-scala-plugin:maven-plugin:2.13

from the specified remote repositories:
nexus-public-snapshots
(http://aedea.abstra:8081/nexus/content/groups/public-snapshots),
nexus (http://aedea.abstra:8081/nexus/content/groups/public)

[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 minutes 2 seconds
[INFO] Finished at: Mon Nov 23 14:26:04 CET 2009
[INFO] Final Memory: 33M/79M
rg/repo-releases)

Regards,
-Mario.

--
I want to change the world but they won't give me the source code.

[scala-tools] [ANN] maven-scala-plugin 2.13

2009-11-22T12:30:05Z

The maven-scala-plugin team is pleased to announce the maven-scala-plugin-2.13 release!

The maven-scala-plugin is used for compiling/testing/running/documenting scala code in maven.

Changes in this version include:

New features:
o compile, test-compile, cc log the root directories of compilation of the list of files that will be compiled (to allow editor/IDE to reset markers/annotation)
o prepare integration of scala-tool-server (sts) with the goal sts-init

Fixed Bugs:
o fix documentation of default value for goal's configuration (http://github.com/davidB/maven-scala-plugin/issues/unreads#issue/16) Issue: 16. Thanks to awhitford.
o fix regression of 2.12 where scala:cc stop/exit at first error Thanks to Christophe Dehlinger.

Changes:
o compile, test-compile, cc compile all files by default (less wrong result with trait,... no more need to clean)
o output line from compiler are redirected to maven's logger in forked mode => prefixed by [ERROR]/[WARN]/[INFO] + ease integration with m2eclipse (FULL_BUILD)
o rename packages inside the plugin to use a "flat one level" : org.scala_tools.maven.xxx => org_scala_tools_maven_xxx (ease file / web browsing)

Have fun!
-maven-scala-plugin team

[scala-tools] Scala Modularisation (Let's see if we can get organized!)

2009-11-21T19:05:35Z

Just so you all know, I'm trying to revive this effort, but can't guarantee too much more than "thought leadership" at this point. Hopefully I can finish up some of my other things soon, but for now I wanted to jot down all the things I had though through a year ago when I first attempted to modularize the scala build.

- Josh

---------- Forwarded message ----------
From: Josh Suereth <joshua.suereth@...>
Date: Sat, Nov 21, 2009 at 10:03 PM
Subject: View this page "Modularization Design"
To: Scala Incubator <scala-incubator@...>

Hey guys, I tried to write down my thoughts, as I said I would
earlier. Let me know what you think. This effort (in my estimation)
will mostly be a build-system redesign at first, with tweaking/moving
of dependencies amongst packages later, and the more advanced modular
designs coming even after that.

Anyway, I tried to take a crack at what the "first step' would be.
Let me know how you all feel about it.

Click on http://groups.google.com/group/scala-incubator/web/modularisation-design
- or copy & paste it into your browser's address bar if that doesn't
work.

[scala-tools] Error highlights in Eclipse Scala

2009-11-21T09:34:30Z

In the 2.8 nightly build the Scala editor displays a lot of error highlights on sources that do not contain errors at all. All the import statements contain an error highlight saying "component is not a member of package xxx" and the the whole source is packed with highlights saying "not found: type xxx".
Sometimes closing the source and reopening it temporarily solves the problem but then they reappear is soon as I start editing.

Is this a known issue?

Gr. Silvio

Re: [scala-tools] Scala Interpreter error

2009-11-21T09:22:51Z

As I don't have any commit-rights, here is the patch that solves the
problem with the interpreter and the eclipse plugin.
There are only a couple of minor changes. I tested the changes in my
development environment and in a freshly installed eclipse. In both
cases, it works well.
It would be great if someone could commit the changes to the repository.

-Johan

Johan Leuenberger wrote:

> thank you Tim.
> Indeed it works. I will make some tests but i think it is a possible
> solution.
>
> -Johan
>
> Tim Clendenen wrote:
>
>> Johan,
>>
>> Adding getBundleEntry("/lib/msil.jar") to the list constructed at the
>> end of interpreterExtraClassPath within the same file as the changes you
>> made takes care of the classpath problem. Same as you, I'm not sure if
>> this is the best or correct fix, but it seems to work.
>>
>> Tim
>>
>> Johan Leuenberger wrote:
>>
>>
>>> I modified the variable mainClass of the doTheLaunch method from
>>> "scala.tools.nsc.MainInterpreter" to
>>> "scala.tools.nsc.MainGenericRunner". So instead of launching an
>>> instance of MainInterpreter, it launchs MainGenericRunner. It seems to
>>> work but i'm not sure that it's the better way to make it work.
>>> by the way, there is still a problem with the classpath...
>>>
>>> -Johan
>>>
>>> Josh Suereth wrote:
>>>
>>>
>>>> You need to make sure the InterpreterSettings class is still being
>>>> used. If not, you should probably just use whatever Settings class
>>>> the interpreter uses to load in settings. I have another project I
>>>> use at work where I can validate that (the code probably changed
>>>> after 2.7.x).
>>>>
>>>> Also, the classpath that was generated used to use the wrong
>>>> algorithm for determining jar locations. I"m not sure if this was
>>>> updated by miles or not. I'm currently in a crunch at work for
>>>> beta, but hopefully i can guide you correctly this weekend.
>>>>
>>>>
>>>> - Josh
>>>>
>>>> On Wed, Nov 18, 2009 at 5:46 PM, Johan Leuenberger
>>>> <johan.leuenberger@... <mailto:johan.leuenberger@...>> wrote:
>>>>
>>>> It would be great if I could help fix this bug. I have a working
>>>> development environment and i looked at the code but i don't see
>>>> where the problem is located. May the errors is in the
>>>> InterpreterLaunchConfigurationDelegate class or where else?
>>>>
>>>> -Johan
>>>>
>>>> Josh Suereth wrote:
>>>>
>>>> I apologize. I haven't had time to keep up/maintain the scala
>>>> interpreter/console in Eclipse. I'm pretty sure things have
>>>> changed enough on trunk to break. I would like to say I'd fix
>>>> it, but unfortunately, the amount of time it takes to set up a
>>>> development enivornment for the Eclipse Scala plugin on my
>>>> machine usually entails my entire free time for that day. If
>>>> there's someone else who is maintaining a development
>>>> environment, I can guide you through the process of fixing the
>>>> interpreter, but unfrouantely can't commit to doing this myself.
>>>>
>>>> BTW this looks like a valid bug.
>>>>
>>>> - Josh
>>>>
>>>> On Tue, Nov 17, 2009 at 8:18 PM, Johan Leuenberger
>>>> <johan.leuenberger@... <mailto:johan.leuenberger@...>
>>>> <mailto:johan.leuenberger@...
>>>> <mailto:johan.leuenberger@...>>> wrote:
>>>>
>>>> Hello,
>>>> There is an error when I try to run the Scala Interpreter in
>>>> Eclipse(v3.5.1) using the latest Scala nightly plugin.
>>>> Here is how to recreate the bug:
>>>> right-click on the Scala project, Scala -> Create Scala
>>>> Interpreter.
>>>>
>>>> Console output:
>>>> -----------------------------
>>>>
>>>> Welcome to Scala version 2.8.0.r19682-b20091117020214 (Java
>>>> HotSpot(TM) Server VM, Java 1.6.0_15).
>>>> Type in expressions to have them evaluated.
>>>> Type :help for more information.
>>>>
>>>> scala> <script>:9: error: not found: type Interpreter
>>>> class InterpreterSettings(repl: Interpreter) {
>>>> ^
>>>> <script>:3: error: type InterpreterSettings is not a
>>>> member of
>>>> package scala.tools.nsc
>>>> var value: scala.tools.nsc.InterpreterSettings = _
>>>> ^
>>>> Exception in thread "main"
>>>> java.util.NoSuchElementException: None.get
>>>> at scala.None$.get(Option.scala:169)
>>>> at scala.None$.get(Option.scala:167)
>>>> at
>>>>
>>>> scala.tools.nsc.Interpreter.scala$tools$nsc$Interpreter$$loadByName(Interpreter.scala:151)
>>>>
>>>> at scala.tools.nsc.Interpreter.bind(Interpreter.scala:467)
>>>> at
>>>>
>>>> scala.tools.nsc.InterpreterLoop$$anonfun$bindSettings$1.apply(InterpreterLoop.scala:124)
>>>>
>>>> at
>>>>
>>>> scala.tools.nsc.InterpreterLoop$$anonfun$bindSettings$1.apply(InterpreterLoop.scala:122)
>>>>
>>>> at
>>>>
>>>> scala.tools.nsc.Interpreter$$anonfun$beQuietDuring$2.apply(Interpreter.scala:100)
>>>>
>>>> at
>>>> scala.util.control.Exception$Catch.apply(Exception.scala:79)
>>>> at
>>>> scala.tools.nsc.Interpreter.beQuietDuring(Interpreter.scala:98)
>>>> at
>>>>
>>>> scala.tools.nsc.InterpreterLoop.bindSettings(InterpreterLoop.scala:122)
>>>> at
>>>> scala.tools.nsc.InterpreterLoop.repl(InterpreterLoop.scala:218)
>>>> at
>>>> scala.tools.nsc.InterpreterLoop.main(InterpreterLoop.scala:379)
>>>> at
>>>> scala.tools.nsc.InterpreterLoop.main(InterpreterLoop.scala:415)
>>>> at
>>>> scala.tools.nsc.MainInterpreter$.main(MainInterpreter.scala:12)
>>>> at
>>>> scala.tools.nsc.MainInterpreter.main(MainInterpreter.scala)
>>>> <script>:4: error: type InterpreterSettings is not a
>>>> member of
>>>> package scala.tools.nsc
>>>> def set(x: Any) = value =
>>>> x.asInstanceOf[scala.tools.nsc.InterpreterSettings]
>>>> ^
>>>> ---------------------------
>>>>
>>>> Johan
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>
>

Index: src/scala/tools/eclipse/interpreter/InterpreterLaunchConfigurationDelegate.scala
===================================================================
--- src/scala/tools/eclipse/interpreter/InterpreterLaunchConfigurationDelegate.scala (revision 19761)
+++ src/scala/tools/eclipse/interpreter/InterpreterLaunchConfigurationDelegate.scala (working copy)
@@ -19,7 +19,7 @@
val mon : IProgressMonitor = if(monitor == null) new NullProgressMonitor() else monitor
//Helper method to actually perform the launch inside a try-catch block.
def doTheLaunch() {
- val mainClass = "scala.tools.nsc.MainInterpreter"
+ val mainClass = "scala.tools.nsc.MainGenericRunner"

mon.beginTask(configuration.getName(), 3); //$NON-NLS-1$
//We need lots of early outs if possible...
@@ -145,6 +145,6 @@
}
// The compiler if scala.tools.nsc is unexploded
// The compiler if scala.tools.nsc is exploded in an outer workspace
- getBundleEntry("/") :: getBundleEntry("/bin"):: getBundleEntry("/lib/fjbg.jar") :: Nil
+ getBundleEntry("/") :: getBundleEntry("/bin"):: getBundleEntry("/lib/fjbg.jar") :: getBundleEntry("/lib/msil.jar") :: Nil
}
}

Re: [scala-tools] Scala Interpreter error

2009-11-21T07:20:53Z

thank you Tim.
Indeed it works. I will make some tests but i think it is a possible
solution.

-Johan

Tim Clendenen wrote:

> Johan,
>
> Adding getBundleEntry("/lib/msil.jar") to the list constructed at the
> end of interpreterExtraClassPath within the same file as the changes you
> made takes care of the classpath problem. Same as you, I'm not sure if
> this is the best or correct fix, but it seems to work.
>
> Tim
>
> Johan Leuenberger wrote:
>
>> I modified the variable mainClass of the doTheLaunch method from
>> "scala.tools.nsc.MainInterpreter" to
>> "scala.tools.nsc.MainGenericRunner". So instead of launching an
>> instance of MainInterpreter, it launchs MainGenericRunner. It seems to
>> work but i'm not sure that it's the better way to make it work.
>> by the way, there is still a problem with the classpath...
>>
>> -Johan
>>
>> Josh Suereth wrote:
>>
>>> You need to make sure the InterpreterSettings class is still being
>>> used. If not, you should probably just use whatever Settings class
>>> the interpreter uses to load in settings. I have another project I
>>> use at work where I can validate that (the code probably changed
>>> after 2.7.x).
>>>
>>> Also, the classpath that was generated used to use the wrong
>>> algorithm for determining jar locations. I"m not sure if this was
>>> updated by miles or not. I'm currently in a crunch at work for
>>> beta, but hopefully i can guide you correctly this weekend.
>>>
>>>
>>> - Josh
>>>
>>> On Wed, Nov 18, 2009 at 5:46 PM, Johan Leuenberger
>>> <johan.leuenberger@... <mailto:johan.leuenberger@...>> wrote:
>>>
>>> It would be great if I could help fix this bug. I have a working
>>> development environment and i looked at the code but i don't see
>>> where the problem is located. May the errors is in the
>>> InterpreterLaunchConfigurationDelegate class or where else?
>>>
>>> -Johan
>>>
>>> Josh Suereth wrote:
>>>
>>> I apologize. I haven't had time to keep up/maintain the scala
>>> interpreter/console in Eclipse. I'm pretty sure things have
>>> changed enough on trunk to break. I would like to say I'd fix
>>> it, but unfortunately, the amount of time it takes to set up a
>>> development enivornment for the Eclipse Scala plugin on my
>>> machine usually entails my entire free time for that day. If
>>> there's someone else who is maintaining a development
>>> environment, I can guide you through the process of fixing the
>>> interpreter, but unfrouantely can't commit to doing this myself.
>>>
>>> BTW this looks like a valid bug.
>>>
>>> - Josh
>>>
>>> On Tue, Nov 17, 2009 at 8:18 PM, Johan Leuenberger
>>> <johan.leuenberger@... <mailto:johan.leuenberger@...>
>>> <mailto:johan.leuenberger@...
>>> <mailto:johan.leuenberger@...>>> wrote:
>>>
>>> Hello,
>>> There is an error when I try to run the Scala Interpreter in
>>> Eclipse(v3.5.1) using the latest Scala nightly plugin.
>>> Here is how to recreate the bug:
>>> right-click on the Scala project, Scala -> Create Scala
>>> Interpreter.
>>>
>>> Console output:
>>> -----------------------------
>>>
>>> Welcome to Scala version 2.8.0.r19682-b20091117020214 (Java
>>> HotSpot(TM) Server VM, Java 1.6.0_15).
>>> Type in expressions to have them evaluated.
>>> Type :help for more information.
>>>
>>> scala> <script>:9: error: not found: type Interpreter
>>> class InterpreterSettings(repl: Interpreter) {
>>> ^
>>> <script>:3: error: type InterpreterSettings is not a
>>> member of
>>> package scala.tools.nsc
>>> var value: scala.tools.nsc.InterpreterSettings = _
>>> ^
>>> Exception in thread "main"
>>> java.util.NoSuchElementException: None.get
>>> at scala.None$.get(Option.scala:169)
>>> at scala.None$.get(Option.scala:167)
>>> at
>>>
>>> scala.tools.nsc.Interpreter.scala$tools$nsc$Interpreter$$loadByName(Interpreter.scala:151)
>>>
>>> at scala.tools.nsc.Interpreter.bind(Interpreter.scala:467)
>>> at
>>>
>>> scala.tools.nsc.InterpreterLoop$$anonfun$bindSettings$1.apply(InterpreterLoop.scala:124)
>>>
>>> at
>>>
>>> scala.tools.nsc.InterpreterLoop$$anonfun$bindSettings$1.apply(InterpreterLoop.scala:122)
>>>
>>> at
>>>
>>> scala.tools.nsc.Interpreter$$anonfun$beQuietDuring$2.apply(Interpreter.scala:100)
>>>
>>> at
>>> scala.util.control.Exception$Catch.apply(Exception.scala:79)
>>> at
>>> scala.tools.nsc.Interpreter.beQuietDuring(Interpreter.scala:98)
>>> at
>>>
>>> scala.tools.nsc.InterpreterLoop.bindSettings(InterpreterLoop.scala:122)
>>> at
>>> scala.tools.nsc.InterpreterLoop.repl(InterpreterLoop.scala:218)
>>> at
>>> scala.tools.nsc.InterpreterLoop.main(InterpreterLoop.scala:379)
>>> at
>>> scala.tools.nsc.InterpreterLoop.main(InterpreterLoop.scala:415)
>>> at
>>> scala.tools.nsc.MainInterpreter$.main(MainInterpreter.scala:12)
>>> at
>>> scala.tools.nsc.MainInterpreter.main(MainInterpreter.scala)
>>> <script>:4: error: type InterpreterSettings is not a
>>> member of
>>> package scala.tools.nsc
>>> def set(x: Any) = value =
>>> x.asInstanceOf[scala.tools.nsc.InterpreterSettings]
>>> ^
>>> ---------------------------
>>>
>>> Johan
>>>
>>>
>>>
>>>
>>>
>>
>>

[scala-tools] Mailing list reminder: Scala-tools

2009-11-21T06:32:02Z

Welcome to the "Scala-tools" mailing list.

This automatic reminder is sent once a month to the list,
to keep subscribers up-to-date with the mailing list services,
and to help keeping the list on topic.

-------------------------------------------------------------------

The "Scala-tools" mailing list:

This list is devoted to all the community-contributed
tools and frameworks developed specifically for the
Scala language, as well as plugins and modules aimed
at integrating existing tools and the Scala system.

Examples are the Scala IDE plugins, sbaz, scalap, and
the many available editor plugins, but the
discussion can also cover sbt, Specs, ScalaTest, etc.

The set of topics that are discussed on this list
include both the usage of these tools, as well as
their development. For instance, this list is
frequently used to discuss the development and usage
of the Eclipse plugin.

Occasionally discussed on the list are also access
to the scala-tools.org website (maintained by the
Scala community and not by EPFL) and Maven
integration, as well as the Lift framework.

More rarely discussed, however, is the use of
general third-party tools that require no specific
integration effort in order to be usable with Scala.

If you are interested, for instance, in using some
specific Java library from Scala, your question is
more appropriately directed to "scala-user" instead.

-------------------------------------------------------------------

Other information:

There are several Scala lists devoted to individual topics (and
more may be created in the future). For the full list, please
see: http://www.scala-lang.org/node/199

Try to avoid cross-posting whenever possible. If you can, select
the list that is closer to your topic and post in that list only.
In any case, never cross-post replies.

If you ever want to unsubscribe from this list, just follow the
instructions on this page:
http://listes.epfl.ch/doc_en.cgi?liste=scala-tools

Thank you!
The Scala Team

Re: [scala-tools] Scala Interpreter error

2009-11-21T00:01:17Z

Johan,

Adding getBundleEntry("/lib/msil.jar") to the list constructed at the
end of interpreterExtraClassPath within the same file as the changes you
made takes care of the classpath problem. Same as you, I'm not sure if
this is the best or correct fix, but it seems to work.

Tim

Johan Leuenberger wrote:

> I modified the variable mainClass of the doTheLaunch method from
> "scala.tools.nsc.MainInterpreter" to
> "scala.tools.nsc.MainGenericRunner". So instead of launching an
> instance of MainInterpreter, it launchs MainGenericRunner. It seems to
> work but i'm not sure that it's the better way to make it work.
> by the way, there is still a problem with the classpath...
>
> -Johan
>
> Josh Suereth wrote:
>> You need to make sure the InterpreterSettings class is still being
>> used. If not, you should probably just use whatever Settings class
>> the interpreter uses to load in settings. I have another project I
>> use at work where I can validate that (the code probably changed
>> after 2.7.x).
>>
>> Also, the classpath that was generated used to use the wrong
>> algorithm for determining jar locations. I"m not sure if this was
>> updated by miles or not. I'm currently in a crunch at work for
>> beta, but hopefully i can guide you correctly this weekend.
>>
>>
>> - Josh
>>
>> On Wed, Nov 18, 2009 at 5:46 PM, Johan Leuenberger
>> <johan.leuenberger@... <mailto:johan.leuenberger@...>> wrote:
>>
>> It would be great if I could help fix this bug. I have a working
>> development environment and i looked at the code but i don't see
>> where the problem is located. May the errors is in the
>> InterpreterLaunchConfigurationDelegate class or where else?
>>
>> -Johan
>>
>> Josh Suereth wrote:
>>
>> I apologize. I haven't had time to keep up/maintain the scala
>> interpreter/console in Eclipse. I'm pretty sure things have
>> changed enough on trunk to break. I would like to say I'd fix
>> it, but unfortunately, the amount of time it takes to set up a
>> development enivornment for the Eclipse Scala plugin on my
>> machine usually entails my entire free time for that day. If
>> there's someone else who is maintaining a development
>> environment, I can guide you through the process of fixing the
>> interpreter, but unfrouantely can't commit to doing this myself.
>>
>> BTW this looks like a valid bug.
>>
>> - Josh
>>
>> On Tue, Nov 17, 2009 at 8:18 PM, Johan Leuenberger
>> <johan.leuenberger@... <mailto:johan.leuenberger@...>
>> <mailto:johan.leuenberger@...
>> <mailto:johan.leuenberger@...>>> wrote:
>>
>> Hello,
>> There is an error when I try to run the Scala Interpreter in
>> Eclipse(v3.5.1) using the latest Scala nightly plugin.
>> Here is how to recreate the bug:
>> right-click on the Scala project, Scala -> Create Scala
>> Interpreter.
>>
>> Console output:
>> -----------------------------
>>
>> Welcome to Scala version 2.8.0.r19682-b20091117020214 (Java
>> HotSpot(TM) Server VM, Java 1.6.0_15).
>> Type in expressions to have them evaluated.
>> Type :help for more information.
>>
>> scala> <script>:9: error: not found: type Interpreter
>> class InterpreterSettings(repl: Interpreter) {
>> ^
>> <script>:3: error: type InterpreterSettings is not a
>> member of
>> package scala.tools.nsc
>> var value: scala.tools.nsc.InterpreterSettings = _
>> ^
>> Exception in thread "main"
>> java.util.NoSuchElementException: None.get
>> at scala.None$.get(Option.scala:169)
>> at scala.None$.get(Option.scala:167)
>> at
>>
>> scala.tools.nsc.Interpreter.scala$tools$nsc$Interpreter$$loadByName(Interpreter.scala:151)
>>
>> at scala.tools.nsc.Interpreter.bind(Interpreter.scala:467)
>> at
>>
>> scala.tools.nsc.InterpreterLoop$$anonfun$bindSettings$1.apply(InterpreterLoop.scala:124)
>>
>> at
>>
>> scala.tools.nsc.InterpreterLoop$$anonfun$bindSettings$1.apply(InterpreterLoop.scala:122)
>>
>> at
>>
>> scala.tools.nsc.Interpreter$$anonfun$beQuietDuring$2.apply(Interpreter.scala:100)
>>
>> at
>> scala.util.control.Exception$Catch.apply(Exception.scala:79)
>> at
>> scala.tools.nsc.Interpreter.beQuietDuring(Interpreter.scala:98)
>> at
>>
>> scala.tools.nsc.InterpreterLoop.bindSettings(InterpreterLoop.scala:122)
>> at
>> scala.tools.nsc.InterpreterLoop.repl(InterpreterLoop.scala:218)
>> at
>> scala.tools.nsc.InterpreterLoop.main(InterpreterLoop.scala:379)
>> at
>> scala.tools.nsc.InterpreterLoop.main(InterpreterLoop.scala:415)
>> at
>> scala.tools.nsc.MainInterpreter$.main(MainInterpreter.scala:12)
>> at
>> scala.tools.nsc.MainInterpreter.main(MainInterpreter.scala)
>> <script>:4: error: type InterpreterSettings is not a
>> member of
>> package scala.tools.nsc
>> def set(x: Any) = value =
>> x.asInstanceOf[scala.tools.nsc.InterpreterSettings]
>> ^
>> ---------------------------
>>
>> Johan
>>
>>
>>
>>
>
>
>

Re: [scala-tools] sub-method code outline, anyone?

2009-11-20T03:15:00Z

On Fri, Nov 20, 2009 at 11:12 AM, Kevin Wright
<kev.lee.wright@...> wrote:
> There's always this:
> http://www.eclipse.org/jdt/ui/astview/index.php

I think the OP is probably after something Scala specific and usable
for code navigation in day to day development ;-)

Cheers,

Miles

--
Miles Sabin
tel: +44 (0)7813 944 528
skype: milessabin
http://www.chuusai.com/
http://twitter.com/milessabin

Re: [scala-tools] sub-method code outline, anyone?

2009-11-20T03:12:24Z

There's always this:

http://www.eclipse.org/jdt/ui/astview/index.php

On Fri, Nov 20, 2009 at 10:48 AM, Miguel Garcia <miguel.garcia@...> wrote:

I'm navigating a Scala codebase with IntelliJ (which is great) and felt the need for a tree-like view displaying the nesting structure *inside* a (really long) method.

Some plugin for any of the major IDEs doing that?

Miguel
http://www.sts.tu-harburg.de/people/mi.garcia

[scala-tools] sub-method code outline, anyone?

2009-11-20T02:48:32Z

I'm navigating a Scala codebase with IntelliJ (which is great) and felt the
need for a tree-like view displaying the nesting structure *inside* a
(really long) method.

Some plugin for any of the major IDEs doing that?

Miguel
http://www.sts.tu-harburg.de/people/mi.garcia

Re: [scala-tools] Commercial Eclipse plugin

2009-11-19T22:31:03Z

On Thursday 19 November 2009 22:08:06 Philip Köster wrote:
> May I answer? I need to `F3' in every declaration to see what is going
> on. (In Eclipse. `F3' is `Open Declaration.)

I'm working with the SVN version, and 'open declaration' seems to work better
every day.

> I need to be able to
> refactor, that is, rename methods, rename packages.

I'm working on that, but it's a lot of work, so don't expect it too soon.

Regards
Mirko

Re: [scala-tools] Commercial Eclipse plugin

2009-11-19T22:02:05Z

On Fri, 2009-11-20 at 00:29 +0000, Mohamed Bana wrote:
> Don't mean to get into an argument. Although the Chrome font
> rendering on Linux seems bad it's (easily) fixable.

I wonder why it needs fixing in the first place.

> And it's no where near as bad as Swing.

It's worse if you don't use the patented FreeType bytecode interpreter
(it's great that some of the patents have expired or are due to expire
though).

> Here's the relevant bug reports;
> http://code.google.com/p/chromium/issues/detail?id=13185
> http://code.google.com/p/chromium/issues/detail?id=26206

Thanks.

Best,
Ismael

Re: [scala-tools] Commercial Eclipse plugin

2009-11-19T16:29:16Z

Don't mean to get into an argument. Although the Chrome font rendering on Linux seems bad it's (easily) fixable. And it's no where near as bad as Swing.

Here's the relevant bug reports;

http://code.google.com/p/chromium/issues/detail?id=13185

http://code.google.com/p/chromium/issues/detail?id=26206

On Thu, Nov 19, 2009 at 11:36 PM, Ismael Juma <mlists@...> wrote:

On Thu, 2009-11-19 at 23:30 +0000, Ricky Clarkson wrote:
> My boss actually cares about stuff like fonts, and claimed that he had
> IDEA working on his Mac with as-good-as-native fonts.

The Mac look and feel is done by Apple and probably uses native fonts.

> I stick with
> the defaults, and I'm not very sensitive to it. Looking at IDEA
> running on my wife's Vista-running laptop right now,

As I said in the other message, Swing uses native font rendering with
the Window look and feel now (since JDK6u10 one of the follow-ups).

> I really can't
> tell the difference between the fonts in Chrome and those in IDEA.

By the way, Chrome fonts on Linux are also bad, but I assume you're
talking about Windows there.

> On Linux, I do notice a difference, but it doesn't bother me.

You're lucky. :)

Ismael