- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
Re: Digest for scala-tools@googlegroups.com - 1 Message in 1 Topic
Fri, 2012-02-10, 22:44
On Fri, Feb 10, 2012 at 4:34 PM, <scala-tools@googlegroups.com> wrote:
Today's Topic SummaryGroup: http://groups.google.com/group/scala-tools/topics
Problem with Kiama migration to Sonatype
- Problem with Kiama migration to Sonatype [1 Update]
Tony Sloane <inkytonik@gmail.com> Feb 10 03:57PM +0100
Does anyone know who is actually doing the migration of projects from scala-tools.org to Sonatype's repository?
My com.googlecode.kiama project is published on scala-tools.org.
One of my users just reported that the
http://scala-tools.org/repo-releases/com/googlecode
address is redirecting to
https://oss.sonatype.org/content/repositories/releases/com/googlecode/
which doesn't contain Kiama, so Kiama is no longer found when sbt looks for it.
I did hear from the Sonatype people about another project of mine (com.googlecode.sbt-rats) and that appears to have been copied across to the Sonatype repo. However, I haven't heard from them about Kiama, it has not been copied and I don't know whether that's an oversight or whether it's just a work in progress.
So, who is actually doing it and how can I find out when things will be accessible again? It's frustrating for these changes to be happening magically without any clear announcements and breaking things for library users...
thanks,
Tony
I had a similar bug report with one of my scala-tools projects as well
You received this message because you are subscribed to the Google Group scala-tools.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.
Sat, 2012-02-11, 15:51
#2
Re: Re: Problem with Kiama migration to Sonatype
On Sat, Feb 11, 2012 at 12:43 AM, Tony Sloane <inkytonik@gmail.com> wrote:
It would have been more social for the scala-tools redirect to wait until all of the projects had moved.
Based on the events leading up to this, that was the point. No going gently into that good night for some of us. Anyone with kids knows that kids sometimes have trouble distinguishing "good attention" and "bad attention", and so too do some of the overgrown children.
The upshot seems to be that if they couldn't work out who was the maintainer of a project, they haven't moved it across since they didn't know who to contact. The result is that all of those projects are now inaccessible since scala-tools.org is redirecting to the Sonatype OSS repo. It would have been more social for the scala-tools redirect to wait until all of the projects had moved.
Until I can find time to work out how to published to Sonatype, not difficult I presume but a time commitment I could do without right now, my library is not usable. Not cool.
Tony