Akka 1.1 Milestone 1 has been released. Akka 1.1-M1 is built on Scala 2.9.0.RC1. The Akka Actor module is now dependency-free.
Release notes can be found at http://doc.akka.io/release-notes
Migration guide at http://doc.akka.io/Migration-1.0-1.1
Artifacts have been published to http://akka.io/repository
Downloads can be found at http://akka.io/downloads
Please help us to test it out.
- Peter
--
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
I haven't had a chance to get onto my dev machine yet today. Does the
new akka-sbt-plugin seem to work okay?
--
Derek
I haven't tested fully yet (with a clean .ivy2 and so on) but yes, a quick test looked fine. Nice work!
Hey Derek,
Tried with a clean .ivy2 - just missing one module configuration. The one for akka itself. I'll let you make the adjustments.
For anyone trying out the 1.1-M1 plugin, add this line to your project:
val akkaModuleConfig = ModuleConfiguration("se.scalablesolutions.akka", AkkaRepositories.Akka_Repository)
- Peter
Ah, that makes sense. Does that interfere with finding Akka that is
published locally? If not then it can be added as a permanent change
to the akka-modules project config and picked up automatically. I'll
be home later today and I'll finally be able to get back on my dev
machine and I'll take a look.
Thanks for having a look!
--
Derek
> On Tue, Apr 5, 2011 at 4:19 AM, Peter Vlugter <pvlu...@gmail.com> wrote:
>> Hey Derek,
>>
>> Tried with a clean .ivy2 - just missing one module configuration. The one for akka itself. I'll let you make the adjustments.
>>
>> For anyone trying out the 1.1-M1 plugin, add this line to your project:
>>
>> val akkaModuleConfig = ModuleConfiguration("se.scalablesolutions.akka", AkkaRepositories.Akka_Repository)
>
> Ah, that makes sense. Does that interfere with finding Akka that is
> published locally?
Yes, it will. Previously we had this line commented out and automatically uncommented on release.
If you need to add something that's used by the release scripts, go for it.
> If not then it can be added as a permanent change
> to the akka-modules project config and picked up automatically. I'll
> be home later today and I'll finally be able to get back on my dev
> machine and I'll take a look.
>
> Thanks for having a look!
>
>
> --
> Derek
>
Another solution is to automatically add it to akka-sbt-plugin when
the project version is not a snapshot.
What do you guys think?
--
Derek
Thanks, can you give an idea of the timeline for a release of 1.1?Is this M1 meant to be one of a series of milestone releases like M2, M3 coming over the coming weeks? Or is it likely that we'd see a 1.1 release candidate as the next release?
Btw, it would be useful to have the date of each release on the release-notes page.- BruceOn Tue, Apr 5, 2011 at 6:09 AM, Peter Vlugter <pvlu...@gmail.com> wrote:
Hi everyone,
Akka 1.1 Milestone 1 has been released. Akka 1.1-M1 is built on Scala 2.9.0.RC1. The Akka Actor module is now dependency-free.
Release notes can be found at http://doc.akka.io/release-notes
Migration guide at http://doc.akka.io/Migration-1.0-1.1
Artifacts have been published to http://akka.io/repository
Downloads can be found at http://akka.io/downloads
Please help us to test it out.
- Peter
--
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
> I had a look at it. The simple solution is to add the line:
> lazy val akkaModuleConfig =
> ModuleConfiguration("se.scalablesolutions.akka", AkkaRepo)
> to AkkaProject.scala in akka-modules, but keep it commented out unless
> we are doing a release. Then it will be automatically added to
> akka-sbt-plugin. This might cause problems during a release build if
> Akka core is not yet been published to the repo.
Let's go for this. Akka will need to be published first, but that's fine.
If you comment it like this:
// release: lazy val akkaModuleConfig ...
it will be automatically uncommented.
> Another solution is to automatically add it to akka-sbt-plugin when
> the project version is not a snapshot.
We may publish snapshot versions so let's go for adding the module config.
Unfortunately not. Backporting is something we charge for.
--
Jonas Bonér
http://scalablesolutions.se
http://jonasboner.com
http://akka.io
http://letitcrash.com
Okay, commited the change, but I'm not able to properly test it as the
test-release scripts doesn't seem to be doing any replacements for me,
it just gives an 'sed' error. I'll have to look into it later, too
busy at the moment, but I think it might have to do with me running on
Linux and most of you are on OSX?
--
Derek
> Hello,
>
> is there a way to build akka 1.1 against scala 2.8.1?
> Other libraries we use don't work with scala 2.9.1.RC0 yet:(
It may be easier to bring those libraries forward to 2.9. Which libraries do you depend on?
Thanks, Derek. Yes, we're on OS X at the moment. I wrote the script with the idea that it would work across the two but didn't test it. The BSD sed may be slightly different for this usage. I'll check it out.
I tried it and it all seems to work well for the plugin. But the module config causes problems with resolving locally for the OSGi module. Maybe we should go for a system property - also makes it possible to publish snapshots from jenkins without using the release scripts. I can look at it later today.
We could just add the Akka repo as a normal repo and let sbt handle it. That shouldn't slow things down too much.
Or I can add the module configuration just to the akka-sbt-plugin.
> We could just add the Akka repo as a normal repo and let sbt handle it. That shouldn't slow things down too much.
>
> Or I can add the module configuration just to the akka-sbt-plugin.
I've just made a change so that it's an akka.release system property for signalling whether to add the module config. This is useful for snapshot releases which won't use the release scripts but a normal publish.
I think we've got it all covered now...
Great. If I get time I want to look into that issue with 'sed'. It
shouldn't be that different between Linux and OSX.
--
Derek
Thanks, much appreciated.