Scala 2.8 and sbaz

Hi James,
yes, sbaz remains part of the Scala release, at least as long as there's no replacementfor it. As mentioned in other threads, we expect to release a 2.8.0beta end of summer, beginning of autumn. We'll keep posting our plans on the mailing lists.
Cheers: Lukas


On Thu, Jul 23, 2009 at 05:23, James Matlik <james.matlik@gmail.com> wrote:

I have recently been able to pick up the sbaz source to add some usability improvements.  Most of what I intend to do is provide the user with more feedback on what sbaz is doing (e.g. download progress) and enhance the dependency collision checks to reduce the likelihood of the working directory from being left in a broken state.  After improving the robustness of the tool, I hope to spend some time nurturing the public universes some.  While this path forward does not include Maven repository integration, at least not directly, it is far more doable given my availablity.

That being said, it sounds like Scala 2.8 is on its way, and I assume sbaz will both continue to be bundled in the Scala release and need to be binary compatible with the 2.8 release.  Is this assumption correct, and if so, would you please keep me informed of time lines?  I don't want to cause any obsticals or delays.

Thanks,
James

Yeah, I've been aware of the other threads on this mailing list, and I understand the 2.8.0 deadline is not known at this time.  My question was more geared toward any deadline that would apply to Sbaz previous to the 2.8.0beta release, if such a thing exists.  I will need some forwarning to be sure it is ready for the beta release, and could use some guidence as to what I should expect from an backward incompatability point of view.  Am I correct that the code should compile to 2.8.0 without change, or is this a neive understanding?  At present (last tried late last week), I do get some error messages under 2.8.0, and if these are supposed to just work, I can look into creating bug tickets.

On a somewhat related note, I have implemented some improvements to the Downloader functionality in the Sbaz library, and have yet to push any changes into SVN.  This won't significantly change Sbaz's functionality (i.e. its backwards compatible), but there is some internal refactoring of the code. Would anyone have concerns with such a change proceeding forward without significant review, or should I submit all my changes to the review board?

A more general question... Where should I draw the line between Sbaz and the rest of the Scala distribution?  Can it be treated as a black box application that, as long as the features are backward compatible or transparently migrated, can evolve without concern of breaking external code?

Thanks,
James

On Thu, Jul 23, 2009 at 6:08 AM, Lukas Rytz <lukas.rytz@epfl.ch> wrote:

Hi James,
yes, sbaz remains part of the Scala release, at least as long as there's no replacementfor it. As mentioned in other threads, we expect to release a 2.8.0beta end of summer, beginning of autumn. We'll keep posting our plans on the mailing lists.
Cheers: Lukas


On Thu, Jul 23, 2009 at 05:23, James Matlik <james.matlik@gmail.com> wrote:

I have recently been able to pick up the sbaz source to add some usability improvements.  Most of what I intend to do is provide the user with more feedback on what sbaz is doing (e.g. download progress) and enhance the dependency collision checks to reduce the likelihood of the working directory from being left in a broken state.  After improving the robustness of the tool, I hope to spend some time nurturing the public universes some.  While this path forward does not include Maven repository integration, at least not directly, it is far more doable given my availablity.

That being said, it sounds like Scala 2.8 is on its way, and I assume sbaz will both continue to be bundled in the Scala release and need to be binary compatible with the 2.8 release.  Is this assumption correct, and if so, would you please keep me informed of time lines?  I don't want to cause any obsticals or delays.

Thanks,
James

Apparently, I am still learning details about sbaz.  I now see that the build script packages the scala-library.jar used to build sbaz within the distribution, making the tool almost completely self contained.  As a result, there is no hard requirement that sbaz be upgraded to 2.8.0 when the beta is released.  I'm not sure how I missed that detail for such a long time...  Unless I hear otherwise, I will assume sbaz is loosely coupled with the rest of the scala release (and supporting tools), and internal design changes will not require rigerous review.

Thanks,
James

On Sat, Aug 1, 2009 at 1:51 PM, James Matlik <james.matlik@gmail.com> wrote:

Yeah, I've been aware of the other threads on this mailing list, and I understand the 2.8.0 deadline is not known at this time.  My question was more geared toward any deadline that would apply to Sbaz previous to the 2.8.0beta release, if such a thing exists.  I will need some forwarning to be sure it is ready for the beta release, and could use some guidence as to what I should expect from an backward incompatability point of view.  Am I correct that the code should compile to 2.8.0 without change, or is this a neive understanding?  At present (last tried late last week), I do get some error messages under 2.8.0, and if these are supposed to just work, I can look into creating bug tickets.

On a somewhat related note, I have implemented some improvements to the Downloader functionality in the Sbaz library, and have yet to push any changes into SVN.  This won't significantly change Sbaz's functionality (i.e. its backwards compatible), but there is some internal refactoring of the code. Would anyone have concerns with such a change proceeding forward without significant review, or should I submit all my changes to the review board?

A more general question... Where should I draw the line between Sbaz and the rest of the Scala distribution?  Can it be treated as a black box application that, as long as the features are backward compatible or transparently migrated, can evolve without concern of breaking external code?

Thanks,
James

On Thu, Jul 23, 2009 at 6:08 AM, Lukas Rytz <lukas.rytz@epfl.ch> wrote:

Hi James,
yes, sbaz remains part of the Scala release, at least as long as there's no replacementfor it. As mentioned in other threads, we expect to release a 2.8.0beta end of summer, beginning of autumn. We'll keep posting our plans on the mailing lists.
Cheers: Lukas


On Thu, Jul 23, 2009 at 05:23, James Matlik <james.matlik@gmail.com> wrote:

I have recently been able to pick up the sbaz source to add some usability improvements.  Most of what I intend to do is provide the user with more feedback on what sbaz is doing (e.g. download progress) and enhance the dependency collision checks to reduce the likelihood of the working directory from being left in a broken state.  After improving the robustness of the tool, I hope to spend some time nurturing the public universes some.  While this path forward does not include Maven repository integration, at least not directly, it is far more doable given my availablity.

That being said, it sounds like Scala 2.8 is on its way, and I assume sbaz will both continue to be bundled in the Scala release and need to be binary compatible with the 2.8 release.  Is this assumption correct, and if so, would you please keep me informed of time lines?  I don't want to cause any obsticals or delays.

Thanks,
James