why ivy version 2.3.0-rc1

[Jeff Olson]

Is there any particular reason why sbt (0.13.0-RC5) is still using ivy version 2.3.0-rc1 instead of the final release 2.3.0 (which was released on Jan 20, 2013)? Oversight, or is there some reason sbt can't upgrade? I'm just curious.

-Jeff

[Paul Phillips]

On Tue, Aug 13, 2013 at 8:13 PM, Jeff Olson <jeff.d...@gmail.com> wrote:

Is there any particular reason why sbt (0.13.0-RC5) is still using ivy version 2.3.0-rc1 instead of the final release 2.3.0 (which was released on Jan 20, 2013)? Oversight, or is there some reason sbt can't upgrade? I'm just curious.

At some point maybe six months ago, in a fit of insanity, I worked on moving forward to the latest release version. I think the impetus was that I discovered the ivy people are still fixing bugs, or at least they are telling their bug tracker they are fixing bugs, and some were the kind of horrible "a small dose of malformed xml poisons the 2gb ivy cache" sort of bugs which have characterized ivy and sbt throughout my time with them and to which I had recently squandered most of a day just trying to obtain a reproduction.

I discovered sbt's code had diverged enough that I couldn't put humpty back together again (I find sbt's codebase is not the easiest to master as a driveby upgrader.) I don't remember the details of the divergence but I do remember some fits of choking, coughing, maybe some labored breathing. Until that adventure I had naively thought that all the ivy-related flailing we encounter was something inflicted on us, the innocent victims, by rogues with unknown motives. But since then I have harbored the sinking feeling that sbt is an active participant.

I have no specific evidence and I'm not going to go trolling the git repo to refresh my memory, so discount this at will. On the other hand, if someone knows one or both codebases well enough to venture an opinion, I'd be glad to have this theory refuted, supported, whatever you got, we're not picky.

[Mark Harrah]

The release process for 2.3.0 has been a bit odd. 2.3.0-rc1 came out April 2012. sbt 0.12.0 was released Aug 1 2012 based on it because it had been two years since 2.2.0, had important fixes, and there was no sign of final. 2.3.0-rc2 came in Nov 2012 (7 months after rc1) and broke two public APIs sbt used, so it couldn't be used in 0.12. One of those breaking changes is minor, but the other one is more involved. 2.3.0 final was in Jan 2013 as you state and I don't remember if I saw the announcement. Looking at it now, I definitely didn't see that it includes fixes not previously in a release candidate. Anyway, it would have been nice to bump to final for 0.13 but it is too late for that at this point. Please open a bug and it will be scheduled for 0.14.0.

-Mark

> -Jeff
>
> --
> You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to simple-build-t...@googlegroups.com.
> To post to this group, send email to simple-b...@googlegroups.com.
> Visit this group at http://groups.google.com/group/simple-build-tool.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Jeff Olson]

Thanks for the info guys. Issue filed: https://github.com/sbt/sbt/issues/847