Problems with akka 1.3.1 (unresolved dependency - se.scalablesolutions.akka - not found)

[Daniel Roziecki]

Hello,

(sowase/*:update) sbt.ResolveException: unresolved dependency: se.scalablesolutions.akka#akka-actor;1.3.1: not found

[error] unresolved dependency: se.scalablesolutions.akka#akka-remote;1.3.1: not found

[error] unresolved dependency: se.scalablesolutions.akka#akka-stm;1.3.1: not found

what happens? Not so long ago (if I good remember last sbt update I did 2 weeks ago), everything works fine, but when I try yesterday it didn't.

I know 1.3.1 is old version, and I am migrating now to the current akka, but first, this is a lot of work to do, you really change a lot of things, and second, current version of this app has to work with 1.3.1, too many other dependencies to change it on the fly.

So how I can get 1.3.1 back? ;)

Regards

Daniel Roziecki

[Patrik Nordwall]

It is in repository: http://repo.akka.io/releases/

The repo.typesafe.com has been discontinued.

/Patrik

--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+...@googlegroups.com.
To post to this group, send email to akka...@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[Daniel Roziecki]

Ok, but after I changed resolver I have another problem:

[warn]  ::::::::::::::::::::::::::::::::::::::::::::::

[warn]  ::          UNRESOLVED DEPENDENCIES         ::

[warn]  ::::::::::::::::::::::::::::::::::::::::::::::

[warn]  :: org.guiceyfruit#guice-all;2.0: not found

[warn]  ::::::::::::::::::::::::::::::::::::::::::::::

[warn]

[warn]  Note: Unresolved dependencies path:

[warn]          org.guiceyfruit:guice-all:2.0

[warn]            +- se.scalablesolutions.akka:akka-typed-actor:1.3.1

[warn]            +- se.scalablesolutions.akka:akka-remote:1.3.1 (/vagrant/dev/sowase/build.sbt#L22-33)

[warn]            +- EMSSIK.NET:sowase_2.9.2:0.0.1

sbt.ResolveException: unresolved dependency: org.guiceyfruit#guice-all;2.0: not found

Regards

Daniel

[Daniel Roziecki]

resolved:

resolvers += "GuiceyFruit Repo" at "http://guiceyfruit.googlecode.com/svn/repo/releases/"

and

"org.guiceyfruit" % "guice-all" % "2.0"

but was quite hard to find.

Regards.

Daniel

[Roland Kuhn]

For a little more background on this change: the fact that these artifacts were available via repo.typesafe.com was unintentional as well as very costly—the latter led to the discovery of the former. Instead of mirroring the whole world we now only host our own artifacts, as it should have been done from the beginning. Akka is completely on Maven Central since version 2.1.0, which implies that all dependencies are there as well, but for older versions “convenience” build configurations will need to be adapted. To make it very clear: of course it is not you who is to blame here. We are truly sorry for the disruption.

Regards,

Roland

Dr. Roland Kuhn
Akka Tech Lead
Typesafe – Reactive apps on the JVM.
twitter: @rolandkuhn

[Daniel Roziecki]

There is no problem (ahh, some is, but I understand, why, and I don't blame anyone :) ).

Btw. Do you know that Akka 1.3.1 don't work with current Java 1.7? I don't know since with version exactly, but problem has started +- 2-3 months ago.

When you try create new actor, everything freeze. I try this on many (just installed) machines, so it is not only one machine problem.

This is really only reason, why I have to migrate this code to the newest akka (new akka means new scala, new scala mean migration to last versions other libraries, small scala hell).

Regards

Daniel

You received this message because you are subscribed to a topic in the Google Groups "Akka User List" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/akka-user/YH0gAULodHg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to akka-user+...@googlegroups.com.

[Roland Kuhn]

Hi Daniel,

18 maj 2015 kl. 07:48 skrev Daniel Roziecki <ems...@emssik.eu>:

There is no problem (ahh, some is, but I understand, why, and I don't blame anyone :) ).

Good to know, thanks!

Btw. Do you know that Akka 1.3.1 don't work with current Java 1.7? I don't know since with version exactly, but problem has started +- 2-3 months ago.

When you try create new actor, everything freeze. I try this on many (just installed) machines, so it is not only one machine problem.

No, this does not ring a bell; in general I would be very surprised if there was any problem running any version of Akka on any JRE from 6 to 8—things might change in Java 9 but that’s a rumor at this point.

Regards,

Roland

This is really only reason, why I have to migrate this code to the newest akka (new akka means new scala, new scala mean migration to last versions other libraries, small scala hell).

Akka 1.3 is already very old, also in the sense that the whole Scala ecosystem was a lot younger than it is today. Nowadays we keep things a lot more stable, Akka 2.4 will very likely be binary compatible with Akka 2.3 for example, and Scala 2.12 only has improvements under the hood and no new language features. We have no trouble releasing Akka against 2.10 and 2.11 with the same code base, I don’t recall there being any pain involved when starting to do so.

Regards,

Roland