Scala 2.10.0-M7 is STAGED! 48 (or more) hours to release w/ M7!

[Josh Suereth]

That's right, if you're the owner of a core community library/framework and would like to announce your support for 2.10.0-M7 with the release anouncement, please do the following:

(1) Build your software against 2.10.0-M7 with 2.10.0-M7 dependencies.

(2) Publish your software somewhere convenient like maven-central or other publicly accessible repository.

(3) Respond to this email with the following:

   (a) Name of your project

   (b) Brief (one sentence) description of the project

   (c) URL for the project website

   (d) Instructions for obtaining the project.

Here's an example for my scala-arm project  (which is published and accurate):

---

Name: Scala-arm

Description:   Scala-arm provides automated resource management to ensure all your resources are closed without all the extra work!

URL:  http://jsuereth.com/scala-arm

Location:    "com.jsuereth" % "scala-arm_2.10.0-M7" % "1.2"

--- 

Note:  The -- is for automated parsing, which I'm going to try for this release.

Thanks for the cooperation everyone!   Let's try this process out again!

[etorreborre]

---

Name: specs2

Description:   specs2 is a library for writing executable software specifications

URL:  http://specs2.org

Location:    "org.specs2" % "specs2_2.10.0-M7" % "1.12.1"

--- 

Note for others: if you want sbt to publish your library with the full scala version "mylib_2.10.0-M7" and not only "mylib_2.10", you should add "crossVersion := CrossVersion.full" to your build.sbt file.

Eric.

[Jason Zaugg]

On Tue, Aug 21, 2012 at 5:52 AM, Josh Suereth <joshua....@gmail.com> wrote:

> Note: The -- is for automated parsing, which I'm going to try for this
> release.
>
> Thanks for the cooperation everyone! Let's try this process out again!

You could extract a lot of useful information from:

https://oss.sonatype.org/service/local/data_index?q=_2.10.0-M6

Following <pomLink> will give the the project description, URL.

-jason

[Jesse Eichar]

Name: Scala-IO Core
Description:   Library for idiomatic IO in Scala
URL: http://jesseeichar.github.com/scala-io-doc/0.4.0/index.html#!/overview/index
Location: "com.github.scala-incubator.io" % "scala-io-core_2.10" % "0.4.1"

Name: Scala-IO Core
Description:   Library for idiomatic Filesystem access in Scala
URL: http://jesseeichar.github.com/scala-io-doc/0.4.0/index.html#!/overview/index
Location:"com.github.scala-incubator.io" % "scala-io-file_2.10" % "0.4.1"

On Tue, Aug 21, 2012 at 5:52 AM, Josh Suereth <joshua....@gmail.com> wrote:

[Jesse Eichar]

After publishing I saw the comment from Eric about getting the full 2.10.0-M7 in the name so I have republished.  

Name: Scala-IO Core
Description:   Library for idiomatic IO in Scala
URL: http://jesseeichar.github.com/scala-io-doc/0.4.0/index.html#!/overview/index

Location: "com.github.scala-incubator.io" % "scala-io-core_2.10.0-M7" % "0.4.1"

Name: Scala-IO Core
Description:   Library for idiomatic Filesystem access in Scala
URL: http://jesseeichar.github.com/scala-io-doc/0.4.0/index.html#!/overview/index

Location:"com.github.scala-incubator.io" % "scala-io-file_2.10.0-M7" % "0.4.1"

Jesse

[Hanns Holger Rutz]

I just realised that some stuff I published strangely got version 2.10 instead of 2.10.0-M7. it seems that before i had in build.sbt

scalaVersion := "2.10.0-M6"

and now i have (which is more convenient for me):

scalaVersion := "2.9.2"

crossScalaVersions := Seq( "2.10.0-M7", "2.9.2" )

and depending on whether that version was published for 2.9.2 or not, i publish either with

$ sbt +publish

or

$ sbt
> set scalaVersion := "2.10.0-M7"
> publish

for the M6 i got:

https://oss.sonatype.org/content/repositories/releases/de/sciss/scalaaudiofile_2.10.0-M6/

in the M7 i now get this:

https://oss.sonatype.org/content/repositories/releases/de/sciss/scalaaudiofile_2.10/

is this something to worry about? i can see that the .pom itself still specifies the milestone:

https://oss.sonatype.org/content/repositories/releases/de/sciss/scalaaudiofile_2.10/0.20/scalaaudiofile_2.10-0.20.pom

--> <dependencies><dependency><groupId>org.scala-lang</groupId><artifactId>scala-library</artifactId><version>2.10.0-M7</version><scope>compile</scope></dependency>


two or three are already on their way to maven central. should i republish them? if so, how? it seems that they _do work_ as a dependency for a 2.10.0-M7 project, though.


thanks for clarification,

.h.h.

[Hanns Holger Rutz]

p.s. it seems this is not a problem of how to set the version in build.sbt versus sbt console, but that i have changed from sbt 0.11.3 to 0.12.0 ? because i cannot reproduce the behaviour i had with publishing for M6.

[Hanns Holger Rutz]

ok, i ran into this apparently:

https://groups.google.com/forum/?fromgroups=#!topic/simple-build-tool/miiQwiuxuIY

so will 'screw' the already published versions :-#

[Hanns Holger Rutz]

> set scalaBinaryVersion := "2.10.0-M7"
> publish

[Bill Venners]

Hi Josh,

We have spent a few hours trying to figure out how to please the scalac ant task in 2.10.0-M7. Tried building it ourselves and inserting print statements, but ended up with different errors. Does anyone know offhand what might have changed? All we get is a usage message:

compile-main:

   [scalac] Compiling 196 source files to /Users/bv/nobkp/delus/r18for210M3/target/jar_contents

   [scalac] Compiling 4 source files to /Users/bv/nobkp/delus/r18for210M3/target/jar_contents

   [scalac] Compiling 0 scala and 3 java source files to /Users/bv/nobkp/delus/r18for210M3/target/jar_contents

   [scalac] Usage: scalac <options> <source files>

   [scalac] where possible standard options include:

   [scalac]   -Dproperty=value           Pass -Dproperty=value directly to the runtime system.

   [scalac]   -J<flag>                   Pass <flag> directly to the runtime system.

   [scalac]   -P:<plugin>:<opt>          Pass an option to a plugin

   [scalac]   -X                         Print a synopsis of advanced options.

   [scalac]   -bootclasspath <path>      Override location of bootstrap class files.

   [scalac]   -classpath <path>          Specify where to find user class files.

   [scalac]   -d <directory|jar>         destination for generated classfiles.

   [scalac]   -dependencyfile <file>     Set dependency tracking file.

   [scalac]   -deprecation               Emit warning and location for usages of deprecated APIs.

   [scalac]   -encoding <encoding>       Specify character encoding used by source files.

   [scalac]   -explaintypes              Explain type errors in more detail.

   [scalac]   -extdirs <path>            Override location of installed extensions.

   [scalac]   -feature                   Emit warning and location for usages of features that should be imported explicitly.

   [scalac]   -g:<level>                 Set level of generated debugging info. (none,source,line,vars,notailcalls) default:vars

   [scalac]   -help                      Print a synopsis of standard options

   [scalac]   -javabootclasspath <path>  Override java boot classpath.

   [scalac]   -javaextdirs <path>        Override java extdirs classpath.

   [scalac]   -language:<feature>        Enable one or more language features.

   [scalac]   -no-specialization         Ignore @specialize annotations.

   [scalac]   -nobootcp                  Do not use the boot classpath for the scala jars.

   [scalac]   -nowarn                    Generate no warnings.

   [scalac]   -optimise                  Generates faster bytecode by applying optimisations to the program

   [scalac]   -print                     Print program with Scala-specific features removed.

   [scalac]   -sourcepath <path>         Specify location(s) of source files.

   [scalac]   -target:<target>           Target platform for object files. All JVM 1.5 targets are deprecated. (jvm-1.5,jvm-1.5-fjbg,jvm-1.5-asm,jvm-1.6,jvm-1.7,msil) default:jvm-1.6

   [scalac]   -toolcp <path>             Add to the runner classpath.

   [scalac]   -unchecked                 Enable additional warnings where generated code depends on assumptions.

   [scalac]   -uniqid                    Uniquely tag all identifiers in debugging output.

   [scalac]   -usejavacp                 Utilize the java.class.path in classpath resolution.

   [scalac]   -verbose                   Output messages about what the compiler is doing.

   [scalac]   -version                   Print product version and exit.

   [scalac]   @<file>                    A text file containing compiler arguments (options and source files)

   [scalac] 

   [scalac] Deprecated settings:

   [scalac]   -make:<policy>             Recompilation detection policy (all,changed,immediate,transitive,transitivenocp) default:all

   [scalac]                                deprecated: this option is unmaintained.  Use sbt or an IDE for selective recompilation.

   [scalac] 

In case it helps, the branch I'm using is:

https://scalatest.googlecode.com/svn/branches/r18for210M7

Thanks for any clues.

Bill

[Bill Venners]

Hi Josh,

Ah, nevermind. Posted 9 minutes too soon probably. Apparently fork=true doesn't work anymore with scalac.

Bill

[Josh Suereth]

Can you report a bug if there is one here?

[Bill Venners]

Hi Josh,

Sure. Though I'm not sure how to tell whether this is a bug or intended. The scalac ant task for 2.10.0-M7 accepts fork="false" but complains about fork="true". We saw the Scala build using something called scalacfork. Not sure if there is an intentional move to do the forking action in a different task. Does anyone know about that? I can try deploying a 2.0 milestone under 2.10.0-M7 with sbt if we're no go with ant. The 1.8 stuff is still on ant. Anyway, we'll keep trying to get it to build. (The reason we were forking in the scalar task had to do with preventing out of memory errors, and the OOMs are back. So we have not yet been able to build successfully under 2.10.0-M7.)

Bill

[Josh Suereth]

I tried to unify the two tasks at one point but the patch was reverted.  One is meant to be public, the other for building scala.  To be frank, I know there was a patch here recently but you are the only consumer of the scalac task I know of.   I'll fix the issue if you report it.

[Bill Venners]

Hi Josh,

Wow, my very own task? Cool. I will report it now. If scalacfork is supposed to be private, then this does sound like a bug. I think the ant tasks may also be used by tools such as buildr and gradle.

Bill

[Josh Suereth]

Gradle moved to zinc, we may want to think about migrating ant tasks that direction as well (or buildr/make folk).

[Nils Kilden-Pedersen]

On Tue, Aug 21, 2012 at 1:48 PM, Josh Suereth <joshua....@gmail.com> wrote:

I tried to unify the two tasks at one point but the patch was reverted.  One is meant to be public, the other for building scala.  To be frank, I know there was a patch here recently but you are the only consumer of the scalac task I know of.

We are a silent group.

[Josh Suereth]

Please report errors!

[Bill Venners]

Hi Josh,

I submitted a Jira Issue: SI-6268.

Bill

[Hanns Holger Rutz]

Here are my updates. Online at https://oss.sonatype.org/content/repositories/releases/de/sciss/ --> should appear in maven central soon.

best, .h.h.


Name: ScalaInterpreterPane
Description: A Swing based front-end for the Scala REPL (interpreter)
URL: https://github.com/Sciss/ScalaInterpreterPane
Location: "de.sciss" %% "scalainterpreterpane" % "1.1.+"


Name: AudioWidgets
Description: Specialized Swing widgets for audio applications in Scala
URL: https://github.com/Sciss/AudioWidgets
Location: "de.sciss" %% "audiowidgets" % "1.0.+"


Name: ScalaAudioWidgets
Description: Scala-Swing wrappers for the AudioWidgets library
URL: https://github.com/Sciss/ScalaAudioWidgets
Location: "de.sciss" %% "scalaaudiowidgets" % "1.0.+"


Name: ScalaAudioFile
Description: A library to read and write uncompressed audio files (AIFF, WAVE, etc.)
URL: https://github.com/Sciss/ScalaAudioFile
Location: "de.sciss" %% "scalaaudiofile" % "1.0.+"


Name: ScalaOSC
Description: A library for OpenSoundControl (OSC), a message protocol used in multi-media applications.
URL: https://github.com/Sciss/ScalaOSC
Location: "de.sciss" %% "scalaosc" % "1.0.+"


Name: ScalaCollider
Description: A sound synthesis library for the SuperCollider server
URL: https://github.com/Sciss/ScalaCollider
Location: "de.sciss" %% "scalacollider" % "1.0.+"


Name: ScalaColliderSwing
Description: A Swing and REPL front-end for ScalaCollider
URL: https://github.com/Sciss/ScalaColliderSwing
Location: "de.sciss" %% "scalacolliderswing" % "1.0.+"


Name: FingerTree
Description: A Scala implementation of the versatile purely functional data structure of the same name.
URL: https://github.com/Sciss/FingerTree
Location: "de.sciss" %% "fingertree" % "1.0.+"


Name: ScissDSP
Description: Collection of DSP algorithms and components for Scala
URL: https://github.com/Sciss/ScissDSP
Location: "de.sciss" %% "scissdsp" % "1.1.+"


Name: SonogramOverview
Description: Sonogram view component for Scala/Swing, calculating offline from audio files
URL: https://github.com/Sciss/SonogramOverview
Location: "de.sciss" %% "sonogramoverview" % "1.1.+"

[etorreborre]

Rectification, this is the correct published release for specs2:

---

Name: specs2

Description:   specs2 is a library for writing executable software specifications

URL:  http://specs2.org

Location:    "org.specs2" % "specs2_2.10.0-M7" % "1.12.1.1"

--- 

E.

[Jason Zaugg]

On Tue, Aug 21, 2012 at 5:52 AM, Josh Suereth <joshua....@gmail.com> wrote:

> That's right, if you're the owner of a core community library/framework and
> would like to announce your support for 2.10.0-M7 with the release
> anouncement, please do the following:
>
> (1) Build your software against 2.10.0-M7 with 2.10.0-M7 dependencies.
> (2) Publish your software somewhere convenient like maven-central or other
> publicly accessible repository.
> (3) Respond to this email with the following:
>
> (a) Name of your project
> (b) Brief (one sentence) description of the project
> (c) URL for the project website
> (d) Instructions for obtaining the project.

---
Name: Scalaz
Description: Type classes and purely functional data structures for Scala.
URL: http://code.google.com/p/scalaz/
Location: "org.scalaz" % "scalaz-core_2.10.0-M7" % "6.0.3"
Location: "org.scalaz" % "scalaz-core_2.10.0-M7" % "6.0.4"
Location: "org.scalaz" % "scalaz-core_2.10.0-M7" % "7.0.0-M3"
---

Additional submodules are also published, but omitted from this list
for brevity.

-jason

[Chris Twiner]

I'd love to release a Scales Xml, but there seems to be a library bug
with flatten on a empty stream - I'll try to get a reproducible case
after some sleep, but here is stack trace fun in case anyone sees the
change:

at scala.collection.Iterator$$anon$2.next(Iterator.scala:38)
at scala.collection.Iterator$$anon$2.next(Iterator.scala:36)
at scala.collection.Iterator$$anon$14.next(Iterator.scala:394)
at scala.collection.IterableLike$class.head(IterableLike.scala:91)
at scala.collection.SeqViewLike$AbstractTransformed.head(SeqViewLike.scala:43)
at scala.collection.immutable.Stream.scala$collection$immutable$Stream$$flatten1$1(Stream.scala:909)
at scala.collection.immutable.Stream.flatten(Stream.scala:914)
at scala.collection.immutable.Stream.flatten(Stream.scala:185)

On Tue, Aug 21, 2012 at 5:52 AM, Josh Suereth <joshua....@gmail.com> wrote:

[Daniel Sobral]

What's the exception?

--
Daniel C. Sobral

I travel to the future all the time.

[Bill Venners]

Hi Josh,

With a bit of memory tweaking we got it to build without forking:

Name: ScalaTest

Description: Simple, clear tests and executable specifications

URL: http://www.scalatest.org

Location: "org.scalatest" % "scalatest_2.10.0-M7" % "1.9-2.10.0-M7-B1"

This one already is built with ScalaCheck for 2.10.0-M7.

Bill

On Monday, August 20, 2012 8:52:08 PM UTC-7, Josh Suereth wrote:

[Jason Zaugg]

On Wed, Aug 22, 2012 at 1:57 AM, Daniel Sobral <dcso...@gmail.com> wrote:
> What's the exception?
>
> On Tue, Aug 21, 2012 at 8:37 PM, Chris Twiner <chris....@gmail.com> wrote:
>> I'd love to release a Scales Xml, but there seems to be a library bug
>> with flatten on a empty stream - I'll try to get a reproducible case
>> after some sleep, but here is stack trace fun in case anyone sees the
>> change:
>>
>> at scala.collection.Iterator$$anon$2.next(Iterator.scala:38)
>> at scala.collection.Iterator$$anon$2.next(Iterator.scala:36)
>> at scala.collection.Iterator$$anon$14.next(Iterator.scala:394)
>> at scala.collection.IterableLike$class.head(IterableLike.scala:91)
>> at scala.collection.SeqViewLike$AbstractTransformed.head(SeqViewLike.scala:43)
>> at scala.collection.immutable.Stream.scala$collection$immutable$Stream$$flatten1$1(Stream.scala:909)
>> at scala.collection.immutable.Stream.flatten(Stream.scala:914)
>> at scala.collection.immutable.Stream.flatten(Stream.scala:185)

It's a view bug.

The exception is: next on empty iterator

val f = SeqViewAFMFMF(...)
f.toList = List(SeqViewFF(...),
List(Path(scales.xml.Elem$NoAttribsElem@f5529b73,1,scales.xml.Elem$QNameOnlyElem@613268c8)),
List(Path(scales.xml.Elem$FullElem@ce849484,1,scales.xml.Elem$QNameOnlyElem@f8d51190),
Path(scales.xml.Elem$FullElem@ce849484,3,scales.xml.Elem$QNameOnlyElem@f8d51190)))
f.iterator.toIterable.flatten = !<next on empty iterator>

More than likely it caused or uncovered by:

https://github.com/scala/scala/commit/caf7eb6b

I'm out of time right now to narrow it down further.

-jason

[Ismael Juma]

Hi Bill,

On Wed, Aug 22, 2012 at 2:55 AM, Bill Venners <bi...@artima.com> wrote:

Name: ScalaTest

Description: Simple, clear tests and executable specifications

URL: http://www.scalatest.org

Location: "org.scalatest" % "scalatest_2.10.0-M7" % "1.9-2.10.0-M7-B1"

Is there a plan to release ScalaTest 2.0 Milestones for Scala 2.10?

Best,

Ismael

[Chris Twiner]

exactly, you truly are a star Jason, said it before and I'll write it
again :-) And sorry Daniel, absolutely right, I should have added the
exception.

As per Jason's example there is data present. I checked against M6
(added another check after the .iterator.toIterable.flatten call) and
saw that indeed it was always evaluating the first element.

Stream 908/909 says:

if (!t.isEmpty)
cons(t.head, flatten1(t.tail))

I'll debug to get the instance of t sorted out and perhaps find a side
effecting hasNext :<

[Rickard Nilsson]

Resubmitting this from the correct address, hopefully it will reach the list this time...

---
Name: ScalaCheck
Description: A powerful tool for automatic unit testing
URL: https://github.com/rickynils/scalacheck
Location: "org.scalacheck" % "scalacheck_2.10.0-M7" % "1.10.0"
---

/ Rickard

[Heiko Seeberger]

Name: scalalogging
Description: Convenient and performant logging in Scala
URL: https://github.com/typesafehub/scalalogging
Location: "com.typesafe" %% "scalalogging-slf4j" % "0.3.0-SNAPSHOT" cross CrossVersion.full

[Chris Twiner]

Hi all,

very much reduced:

val viewed : Iterable[Iterable[Iterable[Int]]] =
List(List(List(0).view).view).view

val filtered = viewed.flatMap{ x => x.flatMap( y => List( y.filter{ _
> 0 } ) ) }

filtered.iterator.toIterable.flatten

will throw. Drop the innermost view and it won't and you'll get the
correct Stream() as the result. Using Nil.view will work, using
List(1 ...) will work, anything as long as the first predicate to
Iterator.filter works.

[Jason Zaugg]

On Wed, Aug 22, 2012 at 12:59 PM, Chris Twiner <chris....@gmail.com> wrote:
> Hi all,
>
> very much reduced:
>
> val viewed : Iterable[Iterable[Iterable[Int]]] =
> List(List(List(0).view).view).view
>
> val filtered = viewed.flatMap{ x => x.flatMap( y => List( y.filter{ _
>> 0 } ) ) }
>
> filtered.iterator.toIterable.flatten
>
> will throw. Drop the innermost view and it won't and you'll get the
> correct Stream() as the result. Using Nil.view will work, using
> List(1 ...) will work, anything as long as the first predicate to
> Iterator.filter works.

Lovely minimization! Can you please lodge a ticket?

BTW, would .iterator suffice in your code, rather than .view?
Iterators have a much smaller surface area than views for
implementation bugs.

-jason

[Miles Sabin]

I've just tripped over the regression relative to M6 illustrated
below. Eugene's just reverted the change that introduced it,

https://github.com/scala/scala/pull/1179

Does this warrant a rebuild of M7?

Cheers,


Miles

scala> import scala.collection.generic.CanBuildFrom
import scala.collection.generic.CanBuildFrom

scala> val cbf = implicitly[CanBuildFrom[Nothing, Nothing, Array[Nothing]]]
cbf: scala.collection.generic.CanBuildFrom[Nothing,Nothing,Array[Nothing]]
= scala.Array$$anon$2@6cd0b6f8

scala> cbf().result
java.lang.Exception: Nothing is a bottom type, therefore its erasure
does not return a value
at scala.reflect.ClassTag$$anon$12.runtimeClass(ClassTag.scala:84)
at scala.reflect.ClassTag$$anon$12.runtimeClass(ClassTag.scala:83)
at scala.collection.mutable.ArrayBuilder$.make(ArrayBuilder.scala:39)
at scala.Array$$anon$2.apply(Array.scala:54)
at scala.Array$$anon$2.apply(Array.scala:52)
at .<init>(<console>:10)
at .<clinit>(<console>)
at .<init>(<console>:7)
at .<clinit>(<console>)
at $print(<console>)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at scala.tools.nsc.interpreter.IMain$ReadEvalPrint.call(IMain.scala:732)
at scala.tools.nsc.interpreter.IMain$Request.loadAndRun(IMain.scala:981)
at scala.tools.nsc.interpreter.IMain.loadAndRunReq$1(IMain.scala:571)
at scala.tools.nsc.interpreter.IMain.interpret(IMain.scala:602)
at scala.tools.nsc.interpreter.IMain.interpret(IMain.scala:566)
at scala.tools.nsc.interpreter.ILoop.reallyInterpret$1(ILoop.scala:745)
at scala.tools.nsc.interpreter.ILoop.interpretStartingWith(ILoop.scala:790)
at scala.tools.nsc.interpreter.ILoop.command(ILoop.scala:702)
at scala.tools.nsc.interpreter.ILoop.processLine$1(ILoop.scala:566)
at scala.tools.nsc.interpreter.ILoop.innerLoop$1(ILoop.scala:573)
at scala.tools.nsc.interpreter.ILoop.loop(ILoop.scala:576)
at scala.tools.nsc.interpreter.ILoop$$anonfun$process$1.apply$mcZ$sp(ILoop.scala:867)
at scala.tools.nsc.interpreter.ILoop$$anonfun$process$1.apply(ILoop.scala:822)
at scala.tools.nsc.interpreter.ILoop$$anonfun$process$1.apply(ILoop.scala:822)
at scala.tools.nsc.util.ScalaClassLoader$.savingContextLoader(ScalaClassLoader.scala:135)
at scala.tools.nsc.interpreter.ILoop.process(ILoop.scala:822)
at scala.tools.nsc.MainGenericRunner.runTarget$1(MainGenericRunner.scala:83)
at scala.tools.nsc.MainGenericRunner.process(MainGenericRunner.scala:96)
at scala.tools.nsc.MainGenericRunner$.main(MainGenericRunner.scala:105)
at scala.tools.nsc.MainGenericRunner.main(MainGenericRunner.scala)

On Tue, Aug 21, 2012 at 4:52 AM, Josh Suereth <joshua....@gmail.com> wrote:
> That's right, if you're the owner of a core community library/framework and
> would like to announce your support for 2.10.0-M7 with the release
> anouncement, please do the following:
>
> (1) Build your software against 2.10.0-M7 with 2.10.0-M7 dependencies.
> (2) Publish your software somewhere convenient like maven-central or other
> publicly accessible repository.
> (3) Respond to this email with the following:
>
> (a) Name of your project
> (b) Brief (one sentence) description of the project
> (c) URL for the project website
> (d) Instructions for obtaining the project.
>
>
> Here's an example for my scala-arm project (which is published and
> accurate):
>
> ---
> Name: Scala-arm
> Description: Scala-arm provides automated resource management to ensure
> all your resources are closed without all the extra work!
> URL: http://jsuereth.com/scala-arm
> Location: "com.jsuereth" % "scala-arm_2.10.0-M7" % "1.2"
> ---
>
> Note: The -- is for automated parsing, which I'm going to try for this
> release.
>
> Thanks for the cooperation everyone! Let's try this process out again!

--
Miles Sabin
tel: +44 7813 944 528
skype: milessabin
gtalk: mi...@milessabin.com
g+: http://www.milessabin.com
http://twitter.com/milessabin

[martin odersky]

On Wed, Aug 22, 2012 at 2:19 PM, Miles Sabin <mi...@milessabin.com> wrote:

I've just tripped over the regression relative to M6 illustrated
below. Eugene's just reverted the change that introduced it,

  https://github.com/scala/scala/pull/1179

Does this warrant a rebuild of M7?

I think we can wait for the next release, which will be hopefully RC1.

Cheers

 - Martin

--
Martin Odersky
Prof., EPFL and Chairman, Typesafe
PSED, 1015 Lausanne, Switzerland
Tel. EPFL: +41 21 693 6863
Tel. Typesafe: +41 21 691 4967

[Grzegorz Kossakowski]

On 22 August 2012 12:19, Miles Sabin <mi...@milessabin.com> wrote:

I've just tripped over the regression relative to M6 illustrated
below. Eugene's just reverted the change that introduced it,

  https://github.com/scala/scala/pull/1179

Does this warrant a rebuild of M7?

That's not possible. Once you push a tag in Git it's immutable.

--
Grzegorz Kossakowski

[Chris Twiner]

On Wed, Aug 22, 2012 at 1:28 PM, Jason Zaugg <jza...@gmail.com> wrote:
> On Wed, Aug 22, 2012 at 12:59 PM, Chris Twiner <chris....@gmail.com> wrote:
>> Hi all,
>>
>> very much reduced:
>>
>> val viewed : Iterable[Iterable[Iterable[Int]]] =
>> List(List(List(0).view).view).view
>>
>> val filtered = viewed.flatMap{ x => x.flatMap( y => List( y.filter{ _
>>> 0 } ) ) }
>>
>> filtered.iterator.toIterable.flatten
>>
>> will throw. Drop the innermost view and it won't and you'll get the
>> correct Stream() as the result. Using Nil.view will work, using
>> List(1 ...) will work, anything as long as the first predicate to
>> Iterator.filter works.
>
> Lovely minimization! Can you please lodge a ticket?

I'd be more than happy to oblige but there doesn't seem to be an M7
version yet :-)

> BTW, would .iterator suffice in your code, rather than .view?
> Iterators have a much smaller surface area than views for
> implementation bugs.

Its a small portion of code, and now I've proved its not a bug in my
code I'm happy to release with a caveat against M7.

The XPath code works against any Iterable and a suitable CBF. I've
not found the lazy / view approach to be enough of a significant
performance gain when combining many predicates to make it the primary
choice, but if you really only want to find the first match in a large
doc it can be compelling, so I provide the tools if users want to.

It might be interesting to look at abstracting Iterable vs Iterator
now I've got a very stable base however - sounds fun. I'll give that
a look for 0.7 perhaps.

[Josh Suereth]

Absolutely not.  The only possible options are releasing an M8 or RC1.   I think perhaps we can wait for RC1.   Do you want shapeless in the community build?  This will get you on nightlies and ensure you build before an RC1.

- Josh

[Chris Twiner]

---
Name: Scales Xml
Description: Scales Xml provides superb performance with low memory
usage, a unified pull and push model, Iteratee and Iterator based pull
parsing, equality framework, both an embedded XPath DSL and string
based XPath 1.0 support.
URL: https://github.com/chris-twiner/scalesXml
Location: "org.scalesxml" % "scales-xml_2.10.0-M7" % "0.3.3"
Location: "org.scalesxml" % "scales-xml_2.10.0-M7" % "0.4.3"
---

nb - 0.3.3 is on the way - identical code just on 6.0.3 scalaz - 0.4.3
is travelling to central

The library view bug prevents full functionality but I'm fine with 99% :-)

[Heiko Seeberger]

Update:

Name: ScalaLogging

Description: Convenient and performant logging in Scala
URL: https://github.com/typesafehub/scalalogging

Location: "com.typesafe" %% "scalalogging-slf4j" % "0.3.0" cross CrossVersion.full

Thanks

Heiko

[Roland Kuhn]

--

Name: Akka
Description: Akka is a platform for building highly concurrent, distributed, and fault tolerant event-driven applications on the JVM.
Site: http://akka.io

Location: "com.typesafe.akka" % "akka-actor_2.10.0-M7" % "2.1-M2"
--

Plus the same for all other subprojects:

akka-agent

akka-camel

akka-dataflow

akka-docs

akka-file-mailbox

akka-kernel

akka-mailboxes-common

akka-osgi

akka-osgi-aries

akka-remote

akka-remote-tests

akka-sample-camel

akka-sample-cluster

akka-sample-fsm

akka-sample-hello

akka-sample-hello-kernel

akka-sample-remote

akka-sbt-plugin

akka-slf4j

akka-testkit

akka-transactor

akka-zeromq

New: now published to Sonatype, hopefully to be appearing soon on a Maven Central near you!

Roland Kuhn
Typesafe – The software stack for applications that scale.
twitter: @rolandkuhn

[Tony Sloane]

The first beta of Kiama 1.4.0 using Scala 2.10.0-M7 has been published to Sonatype. it should appear on Maven central in due course. Apart from changes to move to 2.10.0, this version contains a small number of fixes to examples and a couple of bug fixes. 

---

Name: kiama

Description:   Kiama is a language processing library

URL:  http://kiama.googlecode.com

Location:    "com.googlecode.kiama" % "kiama_2.10.0-M7" % "1.4.0-B1"

---

Moving from 2.92 was relatively painless, but I should note that I managed to trigger a compiler crash. I can reproduce it with the full Kiama source by moving one var declaration from within a function literal to outside it, but I have not minimised it yet. I can't see a similar crash in Scala JIRA, so I will report it once I've got a smaller case, hopefully later today.

In the meantime in case someone is interested the top of the stack trace is 

symbol variable count does not exist in org.kiama.rewriting.UniplateTests$$anonfun$9.org$kiama$rewriting$UniplateTests$$anonfun$$uniquevars$1

at scala.reflect.internal.SymbolTable.abort(SymbolTable.scala:48)

at scala.tools.nsc.Global.abort(Global.scala:246)

at scala.tools.nsc.backend.icode.GenICode$ICodePhase.genLoadIdent$1(GenICode.scala:1092)

at scala.tools.nsc.backend.icode.GenICode$ICodePhase.scala$tools$nsc$backend$icode$GenICode$ICodePhase$$genLoad(GenICode.scala:1098)

at scala.tools.nsc.backend.icode.GenICode$ICodePhase$$anonfun$genLoadArguments$1.apply(GenICode.scala:1306)

...

[Paolo G. Giarrusso]

Il giorno mercoledì 22 agosto 2012 03:55:14 UTC+2, Bill Venners ha scritto:

Hi Josh,

With a bit of memory tweaking we got it to build without forking:

Name: ScalaTest

Description: Simple, clear tests and executable specifications

URL: http://www.scalatest.org

Location: "org.scalatest" % "scalatest_2.10.0-M7" % "1.9-2.10.0-M7-B1"

This one already is built with ScalaCheck for 2.10.0-M7.

 

Why do you include the Scala version twice? Scalatest is the only library I know doing that, and it currently makes use from SBT more difficult. Instead of

libraryDependencies += "org.scalatest" %% "scalatest" % "1.9"

plus some trick from https://groups.google.com/forum/?fromgroups=#!topic/simple-build-tool/miiQwiuxuIY, one needs to figure out something like:

libraryDependencies <+= scalaVersion apply (ver => "org.scalatest" % ("scalatest_" + ver) % ("1.9-%s-B2" format ver))

Figuring out this syntax (the use of <+= and apply) is not exactly easy.

Cheers,
Paolo

[Chris Twiner]

is anyone aware of plans for a 2.10.0 M7 sxr release ?