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-RC2 with the
release announcement, please do the following:
(1) Build your software against 2.10.0-RC2 with 2.10.0-RC2 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-RC2" % "1.2"
---
Note: We'll be staging libraries until Thursday COB CEST when we'll be
announcing the RC2 availability.
Technically this isn't the real announcement. That comes Friday. It is
in oss.sonatype.org now, so sbt 0.12.1 can pull it in fine.
And yes, there's a lag before it hits central, but everyone hits that and
delaying a day for each lib is crazy
On Nov 5, 2012 10:26 AM, "Ismael Juma" <ism...@juma.me.uk> wrote:
On Mon, Nov 5, 2012 at 4:48 PM, Josh Suereth <joshua.suer...@gmail.com> wrote:
> Technically this isn't the real announcement. That comes Friday. It is in
> oss.sonatype.org now, so sbt 0.12.1 can pull it in fine.
I don't think it does. I had to add the oss releases resolver to the
sbt.boot.properties. It should work out-of-the box once it has been
propagated to maven central.
On Mon, Nov 5, 2012 at 10:04 AM, Josh Suereth <joshua.suer...@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-RC2 with the release
> announcement, please do the following:
> (1) Build your software against 2.10.0-RC2 with 2.10.0-RC2 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-RC2" % "1.2"
> ---
> Note: We'll be staging libraries until Thursday COB CEST when we'll be
> announcing the RC2 availability.
On 5 Nov 2012, at 15:51, Johannes Rudolph <johannes.rudo...@googlemail.com> wrote:
> I don't think it does. I had to add the oss releases resolver to the
> sbt.boot.properties. It should work out-of-the box once it has been
> propagated to maven central.
I'm confused - I'm certain that I didn't have to jump through these hoops for RC1 - what's different with RC2?
Can someone who's familiar with this help me out with what I need to put in sbt.boot.properties?
--
paul.butcher->msgCount++
Snetterton, Castle Combe, Cadwell Park...
Who says I have a one track mind?
On Mon, Nov 5, 2012 at 5:01 PM, Paul Butcher <p...@paulbutcher.com> wrote:
> I'm confused - I'm certain that I didn't have to jump through these hoops
> for RC1 - what's different with RC2?
It seems to be in maven central now, so everything should be fine.
> On Mon, Nov 5, 2012 at 4:48 PM, Josh Suereth <joshua.suer...@gmail.com>
> wrote:
> > Technically this isn't the real announcement. That comes Friday. It
> is in
> > oss.sonatype.org now, so sbt 0.12.1 can pull it in fine.
> I don't think it does. I had to add the oss releases resolver to the
> sbt.boot.properties. It should work out-of-the box once it has been
> propagated to maven central.
> Johannes
> -----------------------------------------------
> Johannes Rudolph
> http://virtual-void.net
> On Mon, Nov 5, 2012 at 5:01 PM, Paul Butcher <p...@paulbutcher.com> wrote:
>> I'm confused - I'm certain that I didn't have to jump through these hoops
>> for RC1 - what's different with RC2?
> It seems to be in maven central now, so everything should be fine.
On Mon, Nov 5, 2012 at 3:51 PM, Johannes Rudolph <
johannes.rudo...@googlemail.com> wrote:
> On Mon, Nov 5, 2012 at 4:48 PM, Josh Suereth <joshua.suer...@gmail.com>
> wrote:
> > Technically this isn't the real announcement. That comes Friday. It
> is in
> > oss.sonatype.org now, so sbt 0.12.1 can pull it in fine.
> I don't think it does. I had to add the oss releases resolver to the
> sbt.boot.properties. It should work out-of-the box once it has been
> propagated to maven central.
Yes, it doesn't. I tried to update a library and it failed. I would at
least add some information about this in the announcement.
> On Mon, Nov 5, 2012 at 3:51 PM, Johannes Rudolph <
> johannes.rudo...@googlemail.com> wrote:
>> On Mon, Nov 5, 2012 at 4:48 PM, Josh Suereth <joshua.suer...@gmail.com>
>> wrote:
>> > Technically this isn't the real announcement. That comes Friday. It
>> is in
>> > oss.sonatype.org now, so sbt 0.12.1 can pull it in fine.
>> I don't think it does. I had to add the oss releases resolver to the
>> sbt.boot.properties. It should work out-of-the box once it has been
>> propagated to maven central.
> Yes, it doesn't. I tried to update a library and it failed. I would at
> least add some information about this in the announcement.
*(3)* Make sure you've set your cross-building appropriately for RC. This
is what I do because I'm lazy:
scalaVersion := "2.10.0-RC2"
scalaBinaryVersion <<= scalaVersion.identity
These are the three tasks I run on scala-arm to make sure it publishes
immediately after scala itself. If you wish to use any downstream staged
artifacts, you'll need to at least do steps #2 + #3.
Hope that helps!
On Mon, Nov 5, 2012 at 11:16 AM, Josh Suereth <joshua.suer...@gmail.com>wrote:
> Will do. I forgot I had a ~/sbt/repositories file.
> On Nov 5, 2012 11:13 AM, "Ismael Juma" <ism...@juma.me.uk> wrote:
>> On Mon, Nov 5, 2012 at 3:51 PM, Johannes Rudolph <
>> johannes.rudo...@googlemail.com> wrote:
>>> On Mon, Nov 5, 2012 at 4:48 PM, Josh Suereth <joshua.suer...@gmail.com>
>>> wrote:
>>> > Technically this isn't the real announcement. That comes Friday. It
>>> is in
>>> > oss.sonatype.org now, so sbt 0.12.1 can pull it in fine.
>>> I don't think it does. I had to add the oss releases resolver to the
>>> sbt.boot.properties. It should work out-of-the box once it has been
>>> propagated to maven central.
>> Yes, it doesn't. I tried to update a library and it failed. I would at
>> least add some information about this in the announcement.
> 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-RC2 with the release announcement, please do the following:
I just got used to RC1, took a week of vacation, and there's an RC2 already... No source changes were necessary this time, so here we go:
On Tuesday, November 6, 2012 3:50:12 AM UTC+11, Stefan Zeiger wrote:
> On 2012-11-05 16:04, Josh Suereth 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-RC2 with the > release announcement, please do the following:
> I just got used to RC1, took a week of vacation, and there's an RC2 > already... No source changes were necessary this time, so here we go:
> error] last tree to typer: This > [error] symbol: <none> (flags: ) > [error] symbol definition: <none> > [error] symbol owners: > [error] context owners: constructor $anonfun -> anonymous class > $anonfun -> method apply -> anonymous class $anonfun -> method apply -> > anonymous class $anonfun -> method apply -> anonymous class $anonfun -> > method apply -> anonymous class $anonfun -> method apply -> anonymous class > $anonfun -> method apply -> anonymous class $anonfun -> method apply -> > anonymous class $anonfun -> method apply -> anonymous class $anonfun -> > method apply -> anonymous class $anonfun -
> [LOT MORE OF THE SAME HERE]
> > anonymous class $anonfun -> method apply -> anonymous class $anonfun -> > method apply -> anonymous class $anonfun -> method apply -> anonymous class > $anonfun -> method is -> class FeaturesSpec -> package specs2 > [error] > [error] == Enclosing template or block == > [error] > [error] Apply( > [error] super."<init>" > [error] Nil > [error] ) > [error] > [error] uncaught exception during compilation: java.lang.StackOverflowError > [trace] Stack trace suppressed: run last test:compile for the full output. > [error] (test:compile) java.lang.StackOverflowError
> Cheers,
> Eric.
> On Tuesday, November 6, 2012 3:50:12 AM UTC+11, Stefan Zeiger wrote:
>> On 2012-11-05 16:04, Josh Suereth 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-RC2 with the >> release announcement, please do the following:
>> I just got used to RC1, took a week of vacation, and there's an RC2 >> already... No source changes were necessary this time, so here we go:
On Monday, November 5, 2012 9:04:35 AM UTC-6, Josh Suereth 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-RC2 with the > release announcement, please do the following:
> (1) Build your software against 2.10.0-RC2 with 2.10.0-RC2 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-RC2" % "1.2" > ---
> Note: We'll be staging libraries until Thursday COB CEST when we'll be > announcing the RC2 availability.
> 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-RC2 with the release announcement, please do the following:
> (1) Build your software against 2.10.0-RC2 with 2.10.0-RC2 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-RC2" % "1.2"
> ---
> Note: We'll be staging libraries until Thursday COB CEST when we'll be announcing the RC2 availability.
Name: Spire
Description: Powerful new number types and numeric abstractions for Scala.
URL: https://github.com/non/spire Location: "org.spire-math" % "spire_2.10.0-RC2" % "0.3.0-M4"
Published to Sonatype OSS now, should be in Maven Central shortly.
This milestone (M4) introduces a number of new features:
* unsigned number types (UByte through ULong)
* faster sorting and selection
* unboxed extension methods for collections (qsum, qmin, qsorted, etc)
* improved cfor macro
> 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-RC2 with the release announcement, please do the following:
> (1) Build your software against 2.10.0-RC2 with 2.10.0-RC2 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-RC2" % "1.2"
> ---
> Note: We'll be staging libraries until Thursday COB CEST when we'll be announcing the RC2 availability.
On Monday, November 5, 2012 7:04:35 AM UTC-8, Josh Suereth 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-RC2 with the > release announcement, please do the following:
> (1) Build your software against 2.10.0-RC2 with 2.10.0-RC2 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-RC2" % "1.2" > ---
> Note: We'll be staging libraries until Thursday COB CEST when we'll be > announcing the RC2 availability.
On Mon, Nov 5, 2012 at 4:04 PM, Josh Suereth <joshua.suer...@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-RC2 with the
> release announcement, please do the following:
> (1) Build your software against 2.10.0-RC2 with 2.10.0-RC2 dependencies.
> (2) Publish your software somewhere convenient like maven-central or other
> publicly accessible repository.
> (3) Respond to this email with the following:
--- Name: Squeryl Description: A Scala DSL for talking with relational databases with minimum verbosity and maximum type safety URL: http:// <http://jsuereth.com/scala-arm>squeryl.org Location: "org.squeryl" % "squeryl_2.10.0-RC2" % "0.9.5-4" ---
On Monday, November 5, 2012 10:04:35 AM UTC-5, Josh Suereth 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-RC2 with the > release announcement, please do the following:
> (1) Build your software against 2.10.0-RC2 with 2.10.0-RC2 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-RC2" % "1.2" > ---
> Note: We'll be staging libraries until Thursday COB CEST when we'll be > announcing the RC2 availability.
