search

softprops / less-sbt

type less css in your sbt projects
Other
45 stars 18 forks source link

Make clear what repository holds the artifact #18

Closed sirthias closed 12 years ago

sirthias commented 12 years ago

I'm confused about where to find the current artifacts:

Where would I find 0.1.5, 0.1.6 and 0.1.7 ?

melezov commented 12 years ago

Hello @sirthias , I'm glad I'm not the one who is insane :)

0.1.5-0.1.6 were available two days ago but they don't seem to be available anymore. I've also tried all the repositories, best bet would be that they were taken down momentarily.

I'd suggest cloning the repo and publishing locally, it should be a few minutes of your time. This crashed one of my websites so I jammed a jar into its ivy cache manually - should really stop compiling on production machines :P

softprops commented 12 years ago

whoa what? I think this is scala tools messing with me. I've published to my own repo repo.lessis.me while I waited a million years for scala tools to respond to my requests to publish. I only recently got publish access to scala tools so I stopped pushing my own. In the recent weeks I think our good friend dpp decided to step down from owning scala tools without letting someone else take if over and gave us a decent time to pack up and move out. I've gotten some notification from sonatype that my artifacts are being mirrored over to maven central? I've been recommended to go through a second wedding ceremony and request publish access to sonatype. I did that a few days ago but haven't pushed a release there yet. I plan to one I get more of my projects in order.

In should f**k is scala is a messy state for publishing. It's unfortunate that it only adds to the number of things that complain about with scala, scala tooling, and the scala community. I've tried to make some efforts to help out where I can but you can't step away for a few days without a slippery floor tripping you up when you walk back in the room. I think some people feel this with newer versions of sbt coming from older versions (I like the changes) and now its the common publishing host (scala tools).

Sorry for the rant. I had no idea scala tools was actually removing artifacts not just mirroring them else where. I'll take a serious look at this, this weekend. In the mean time I try to do the best job I can with tagging releases religiously. If you have an issue with a mvn/ivy host, we can always fallback on dependable source dependencies!

sirthias commented 12 years ago

Doug, yeah, I'm with you on this. That's why I decided to pull away from the common hosting solution (scala-tools.org et al) for a while and rely on my own repo hosting until the dust settles a bit and some common scala/sbt publishing processes have been established and "worn in"... Seeing that your repo.lessis.me is still up, can't you just go back to pushing your artifacts there?

softprops commented 12 years ago

Yea, sounds like I have to. The only down side is asking users to add an extra resolver. At least I can guarantee things will be where I say they are then :)

sirthias commented 12 years ago

Yes, the extra resolver is certainly a nuisance. However, I figured that its the lesser evil for the moment. Especially since the "new" SBT resolves things much faster than the old one...

denibertovic commented 12 years ago

we can always proxy your repo.lessis.me so we only have to download the artifact once from you and then it stays on our nexus. That's what we do with most repos actually....you save your bandwith and the one hosting the actual repo as well. :)

softprops commented 12 years ago

It looks like more of this was synced up over yesterday or at least partially. When I click the me on http://scala-tools.org/repo-releases/

I not get redirected to https://oss.sonatype.org/content/groups/scala-tools/me/ and see https://oss.sonatype.org/content/repositories/releases/me/lessis/less-sbt_2.9.1_0.11.2/ has all the expected artifacts.

I'll have a closer look at this weekennd and figure out was going on.

sirthias commented 12 years ago

The cause of the issue might be this. If it is then the sonatype rules might force you to host your SBT plugins in your own repo... Sucks...

softprops commented 12 years ago

Crap. Is that true? How did this work with scala tools, also running on nexus I thought? What a crappy state we in :/

jrudolph commented 12 years ago

It's working for me, maybe it was just a temporary hiccup due to part of migration still being in progress?

sroebuck commented 12 years ago

Doug,

Apologies if I didn't copy you in on the correspondence with sonatype on Friday. The files were lost between a backup they used for the transfer to sonatype and the changeset that they updated it with over the days that followed. Those people, like me, who couldn't get hold of less-sbt on Friday and Saturday were just caught in that process.

I can confirm that everything now works thought I can't comment on Tim Perrett tweet and whether this will impact on the uploading of future releases.

softprops commented 12 years ago

http://implicit.ly/less-sbt-019 moved this painfully to sbt community ivy repo tonight. I'll be moving more and more sbt stuff over there through the weekend. Hopefully this will be "the one" for hosting sbt plugins. I've still get to go through the sona ceremony for the rest of my stuff. I can't wait.