- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
RC3 candidate for the first 2.8.0 beta
Thu, 2009-12-17, 15:20
All,
The third release candidate for 2.8.0.Beta1 is available for testing. You
can obtain this candidate from the links below, as well as from the
scala-tools.org Maven repository:
http://www.scala-lang.org/downloads/distrib/files/scala-2.8.0.Beta1-RC3.tgz
http://www.scala-lang.org/downloads/distrib/files/scala-2.8.0.Beta1-RC3.zip
http://www.scala-lang.org/downloads/distrib/files/scala-2.8.0.Beta1-RC3-...
http://www.scala-lang.org/downloads/distrib/files/scala-2.8.0.Beta1-RC3-...
http://www.scala-lang.org/downloads/distrib/files/scala-2.8.0.Beta1-RC3-...
http://www.scala-lang.org/downloads/distrib/files/scala-2.8.0.Beta1-RC3-...
http://www.scala-lang.org/downloads/distrib/files/scala.library_2.8.0.Be...
This is a candidate for the first, preliminary beta release of 2.8.0: it is
only intended to help developers port their code onto the new 2.8
codebase, and it is not production-quality code.
Developers: please try your projects against this initial version and let
us know. Differently from the previous RCs, this candidate is built with
optimization enabled. Please let us know if you find any new problems.
Toni
Thu, 2009-12-17, 21:07
#2
Re: RC3 candidate for the first 2.8.0 beta
I had the same "windowtitle" error with ScalaTest, and "bottom" as well. I removed them temporarily to publish a snapshot, but it would be nice to know how to fix it correctly.
On Thu, Dec 17, 2009 at 1:41 PM, Blair Zajac <blair@orcaware.com> wrote:
On Thu, Dec 17, 2009 at 1:41 PM, Blair Zajac <blair@orcaware.com> wrote:
On 12/17/2009 06:20 AM, Antonio Cunei wrote:
All,
The third release candidate for 2.8.0.Beta1 is available for testing.
You can obtain this candidate from the links below, as well as from the
scala-tools.org Maven repository:
Thanks!
Scala Migrartions successfully passes its test suite.
I do get an error with Scaladocs.
BUILD FAILED
/home/blair/scala-migrations.hg/ant/docs.xml:18: scaladoc doesn't support the "windowtitle" attribute
These seems like a pretty standard attribute to loose, both Javadoc and the previous Scaladoc supported it. Does the new Scaladoc replace the window title dynamically?
Regards,
Blair
Fri, 2009-12-18, 11:27
#3
Re: RC3 candidate for the first 2.8.0 beta
Antonio Cunei wrote:
> Developers: please try your projects against this initial version and
> let us know. Differently from the previous RCs, this candidate is
> built with optimization enabled.
ScalaQuery compiles and passes all tests with RC3.
-sz
Fri, 2009-12-18, 16:47
#4
Re: RC3 candidate for the first 2.8.0 beta
Quite a few of the old Scaladoc options are very much layout-specific. They are modeled on the options provided by Javadoc's standard doclet, which uses the same layout. Options like "bottom", "footer", or "header" do not have a clear meaning in Scaladoc 2, as its standard layout does not have such areas.
What I've done for now is to have two parameters that can be set for Scaladoc:
"-doc-title" (ant "doctitle" attribute): The overall title for the documentation being generated, typically the name of the library or system that is documented.
"-doc-version" (ant "docversion" attribute): Some overall version number for the documentation being generated, typically the version of the library or system that is documented.
For the time being, both parameters have no effect on the generated documentation, but you can change your build scripts to use them. I've added an item in my todo list to actually generate something.
Title and version are relatively abstract notions that make sense in almost any layout (and if it really makes no sense, they can be dropped). In that sense, I think they are more "sustainable" than the old Javadoc options.
Please, send me a note if you think this is the wrong direction to go towards.
Cheers,Gilles.
What I've done for now is to have two parameters that can be set for Scaladoc:
"-doc-title" (ant "doctitle" attribute): The overall title for the documentation being generated, typically the name of the library or system that is documented.
"-doc-version" (ant "docversion" attribute): Some overall version number for the documentation being generated, typically the version of the library or system that is documented.
For the time being, both parameters have no effect on the generated documentation, but you can change your build scripts to use them. I've added an item in my todo list to actually generate something.
Title and version are relatively abstract notions that make sense in almost any layout (and if it really makes no sense, they can be dropped). In that sense, I think they are more "sustainable" than the old Javadoc options.
Please, send me a note if you think this is the wrong direction to go towards.
Cheers,Gilles.
I had the same "windowtitle" error with ScalaTest, and "bottom" as well. I removed them temporarily to publish a snapshot, but it would be nice to know how to fix it correctly.BUILD FAILED
/home/blair/scala-migrations.hg/ant/docs.xml:18: scaladoc doesn't support the "windowtitle" attribute
These seems like a pretty standard attribute to loose, both Javadoc and the previous Scaladoc supported it. Does the new Scaladoc replace the window title dynamically?
Fri, 2009-12-18, 20:57
#5
Re: RC3 candidate for the first 2.8.0 beta
Hmmmm. I recompiled ScalaTest this morning with 2.8.0.Beta1-RC3 and I ran into the error below when trying to run my tests. I figured I'd post the error here in case anybody has already run into this or can point me in the right
direction:
An exception or error caused a run to abort. This may have been caused by a problematic custom reporter.
java.lang.NoSuchMethodError: scala.reflect.Manifest$.Int()Ljava/lang/Object;
at org.scalatest.events.Ordinal.next(Ordinal.scala:184)
at org.scalatest.Tracker.nextOrdinal(Tracker.scala:72)
at org.scalatest.tools.Runner$.doRunRunRunADoRunRun(Runner.scala:1543)
at org.scalatest.tools.Runner$$anonfun$runOptionallyWithPassFailReporter$2.apply(Runner.scala:616)
at org.scalatest.tools.Runner$$anonfun$runOptionallyWithPassFailReporter$2.apply(Runner.scala:615)
at org.scalatest.tools.Runner$.withClassLoaderAndDispatchReporter(Runner.scala:1564)
at org.scalatest.tools.Runner$.runOptionallyWithPassFailReporter(Runner.scala:614)
at org.scalatest.tools.Runner$.run(Runner.scala:517)
at org.scalatest.tools.ScalaTestAntTask.execute(ScalaTestAntTask.scala:259)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
the offending line from Ordinal.scala is:
def nextNewOldPair: (Ordinal, Ordinal) = {
val newArrayForNewSuite = new Array[Int](stamps.length + 1)
val newArrayForOldSuite = new Array[Int](stamps.length)
val zipped = stamps.zipWithIndex // NoSuchMethodError
for ((num, idx) <- zipped) {
newArrayForNewSuite(idx) = num
newArrayForOldSuite(idx) = num
}
newArrayForOldSuite(stamps.length - 1) += 1
(new Ordinal(runStamp, newArrayForNewSuite), new Ordinal(runStamp, newArrayForOldSuite))
}
I tried variations of the code in the REPL but couldn't reproduce the error.
User error or bug?
alex
An exception or error caused a run to abort. This may have been caused by a problematic custom reporter.
java.lang.NoSuchMethodError: scala.reflect.Manifest$.Int()Ljava/lang/Object;
at org.scalatest.events.Ordinal.next(Ordinal.scala:184)
at org.scalatest.Tracker.nextOrdinal(Tracker.scala:72)
at org.scalatest.tools.Runner$.doRunRunRunADoRunRun(Runner.scala:1543)
at org.scalatest.tools.Runner$$anonfun$runOptionallyWithPassFailReporter$2.apply(Runner.scala:616)
at org.scalatest.tools.Runner$$anonfun$runOptionallyWithPassFailReporter$2.apply(Runner.scala:615)
at org.scalatest.tools.Runner$.withClassLoaderAndDispatchReporter(Runner.scala:1564)
at org.scalatest.tools.Runner$.runOptionallyWithPassFailReporter(Runner.scala:614)
at org.scalatest.tools.Runner$.run(Runner.scala:517)
at org.scalatest.tools.ScalaTestAntTask.execute(ScalaTestAntTask.scala:259)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
the offending line from Ordinal.scala is:
def nextNewOldPair: (Ordinal, Ordinal) = {
val newArrayForNewSuite = new Array[Int](stamps.length + 1)
val newArrayForOldSuite = new Array[Int](stamps.length)
val zipped = stamps.zipWithIndex // NoSuchMethodError
for ((num, idx) <- zipped) {
newArrayForNewSuite(idx) = num
newArrayForOldSuite(idx) = num
}
newArrayForOldSuite(stamps.length - 1) += 1
(new Ordinal(runStamp, newArrayForNewSuite), new Ordinal(runStamp, newArrayForOldSuite))
}
I tried variations of the code in the REPL but couldn't reproduce the error.
User error or bug?
alex
Sat, 2009-12-19, 06:27
#6
Re: RC3 candidate for the first 2.8.0 beta
In RC2 I could use both windowtitle and doctitle. Dropping windowtitle
in RC2 changes this in index.html:
- scala-migrations 0.9.2-2.8.0.Beta1-RC2
+ Scala 2
Then going to RC4 without windowtitle.
- Scala 2
+ Scaladoc: all classes and objects
So currently, I don't have a way to set the whole page title to mention
my project's name.
Regards,
Blair
On 12/18/09 7:38 AM, Gilles Dubochet wrote:
> Quite a few of the old Scaladoc options are very much layout-specific.
> They are modeled on the options provided by Javadoc's standard doclet,
> which uses the same layout. Options like "bottom", "footer", or "header"
> do not have a clear meaning in Scaladoc 2, as its standard layout does
> not have such areas.
>
> What I've done for now is to have two parameters that can be set for
> Scaladoc:
>
> "-doc-title" (ant "doctitle" attribute):
> The overall title for the documentation being generated, typically the
> name of the library or system that is documented.
>
> "-doc-version" (ant "docversion" attribute):
> Some overall version number for the documentation being generated,
> typically the version of the library or system that is documented.
>
> For the time being, both parameters have no effect on the generated
> documentation, but you can change your build scripts to use them. I've
> added an item in my todo list to actually generate something.
>
> Title and version are relatively abstract notions that make sense in
> almost any layout (and if it really makes no sense, they can be
> dropped). In that sense, I think they are more "sustainable" than the
> old Javadoc options.
>
> Please, send me a note if you think this is the wrong direction to go
> towards.
>
> Cheers,
> Gilles.
>
>> I had the same "windowtitle" error with ScalaTest, and "bottom" as
>> well. I removed them temporarily to publish a snapshot, but it would
>> be nice to know how to fix it correctly.
>>
>> BUILD FAILED
>> /home/blair/scala-migrations.hg/ant/docs.xml:18: scaladoc doesn't
>> support the "windowtitle" attribute
>>
>> These seems like a pretty standard attribute to loose, both
>> Javadoc and the previous Scaladoc supported it. Does the new
>> Scaladoc replace the window title dynamically?
On 12/17/2009 06:20 AM, Antonio Cunei wrote:
> All,
>
> The third release candidate for 2.8.0.Beta1 is available for testing.
> You can obtain this candidate from the links below, as well as from the
> scala-tools.org Maven repository:
Thanks!
Scala Migrartions successfully passes its test suite.
I do get an error with Scaladocs.
BUILD FAILED
/home/blair/scala-migrations.hg/ant/docs.xml:18: scaladoc doesn't
support the "windowtitle" attribute
These seems like a pretty standard attribute to loose, both Javadoc and
the previous Scaladoc supported it. Does the new Scaladoc replace the
window title dynamically?
Regards,
Blair