ScalaTest 1.7 released, and other news

[Bill Venners]

Hi All,

This morning I released ScalaTest 1.7. Access instructions are here:

http://www.scalatest.org/download

Release notes, with a list of changes is here:

http://www.scalatest.org/release_notes#release17

If you'd like to get an idea of where ScalaTest is heading, Nathan
Hamblen put up a video today from my talk last month at ny-scala here:

http://vimeo.com/36210559

Dick Wall and I will be giving a public Stairway to Scala course to
New York City April 30 to May 4. Info is here:

http://www.artima.com/shop/stairway_to_scala

And I almost can't believe it myself, but look at what book is now in
stock and ready to ship:

http://www.artima.com/shop/actors_in_scala

Please post any ScalaTest 1.7 issues or questions to scalatest-users.

http://groups.google.com/group/scalatest-users

Thanks and enjoy!

Bill
----
Bill Venners
Artima, Inc.
http://www.artima.com

[Jon-Anders Teigen]

Any reason why it has a mandatory dependency on Guice ?

The only reference I can find in the release notes is that TestNG depends on Guice, but TestNG is an optional dependency so is this required Guice dependency a bug ?

<dependency>

<groupId>com.google.inject</groupId>

<artifactId>guice</artifactId>

<version>3.0</version>

</dependency>

http://www.scala-tools.org/repo-releases/org/scalatest/scalatest_2.9.1/1.7/scalatest_2.9.1-1.7.pom

Best Regards

Jon-Anders

--
You received this message because you are subscribed to the Google
Groups "scalatest-users" group.
To post to this group, send email to scalate...@googlegroups.com
To unsubscribe from this group, send email to
scalatest-use...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/scalatest-users?hl=en
ScalaTest itself, and documentation, is available here:
http://www.artima.com/scalatest

[Bill Venners]

Hi Jon,

Yes. Should be optional. Scalatest does not require guide, but the version of sbt that we upgraded to does.

Thanks.

Bill

----

Bill Venners

Artima, Inc.

http://www.artima.com

[Jon-Anders Teigen]

Sorry, but what does sbt have to do with this ?

As far as I can tell the problem is just that <option>true</option> is missing here

http://code.google.com/p/scalatest/source/browse/trunk/pom_template.xml#112

/j

[Bill Venners]

Hi Jon,

Sorry, I meant testng not sbt. Someone asked us to upgrade to a more recent testng, which had some incompatible changes in it and also as far as I understand required us to add the Guice dependency. We forgot to make it optional. Easy to fix, but is it true that the only penalty is users will need to wait once for a download of Guice to their local repos? If so, then this is probably something that can wait to be fixed in 1.8 and not require a 1.7.1? I'm hoping to start the rc process for 1.8 around March 1.

Thanks.

Bill

----

Bill Venners

Artima, Inc.

http://www.artima.com

[Jon-Anders Teigen]

If only it was downloading it to the local repos I don't think anyone would care, but the transitive dependency handling in sbt and maven will not only download, but also put guice and its transitive dependencies on the test classpath.

The result is that users get guice, javax.inject, aopalliance and cglib which again drags in asm all on their test classpath.

I personally don't like seeing bytecode-rewriting libraries on my classpath as it reminds me too much about the rough enterprise-streets of Java I grew up on ;-)

The way around this is to exclude the unwanted dependencies explicitly if you decide to not do another relase is

sbt * https://github.com/harrah/xsbt/wiki/Library-Management

maven * http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html

If you want more bugs to make it worthy a 1.7.1 I also found "AppVersion=1.7.RC2" in the ScalaTestBundle.properties for 1.7

/j

[Bill Venners]

Hi Jon,

Ah, that does sound like a pain. Too bad we didn't notice this during
the RC process. I'll see if anything else is found for a bit.

Can you elaborate on where you saw this:

"AppVersion=1.7.RC2" in the ScalaTestBundle.properties

That is actually rewritten by the build. I just checked my build dirs
and they have the right version, 1.7, in there.

Thanks.

Bill

[Jon-Anders Teigen]

This jar http://www.scala-tools.org/repo-releases/org/scalatest/scalatest_2.9.1/1.7/scalatest_2.9.1-1.7.jar contains AppVersion=1.7.RC2

( also, unsure if this is intended or not, but http://www.scala-tools.org/repo-releases/org/scalatest/scalatest_2.9.1/1.7/scalatest_2.9.1-1.7-sources.jar contains AppVersion=@RELEASE@ )

In addition there seems to be missing a tag for 1.7 at http://code.google.com/p/scalatest/source/browse/#svn%2Ftags

[Bill Venners]

Hi Jon,

That's a serious problem with the redeploy. I ran a tool to redeploy
the same jars I built with 2.9.0 under 2.9.1, and it redeployed the
wrong jars. I'll investigate.

Bill

[Bill Venners]

Hi Jon,

I checked and the releases I built and deployed are fine. Those are
for Scala 2.8.1 and 2.9.0. But the redeploy failed and uploaded the
RC2 jars for 2.8.2, 2.9.0-1, and 2.9.1. I'll have to wait until the
programmer comes back online to help me fix that problem.

Bill

[Bill Venners]

Hi Jon,

Oddly enough, it turned out the redeploy problem was caused by the
darn Guice dependency. Our redeploy task choked when copying because
some extra files in the file set caused by the Guice dependency threw
it off. I fixed this by re-redeploying the proper files after we
enhanced the redeploy task to handle unexpected files in the file set.

What got deployed before accidentally was the 1.7.RC2 files. They went
under scalatest_2.8.2, scalatest_2.9.0-1, and scalatest_2.9.1 artifact
IDs for 1.7. The 1.7 releases I actually built, which were deployed
under scalatest_2.9.0 and scalatest_2.8.1 artifact IDs, were fine
(except for the Guice dependency). Because point releases are binary
compatible now, these builds are good enough for 2.8.2, 2.9.0-1, and
2.9.1. So the builds were fine, just the redeploy copy process screwed
up. I only redeployed the copies, not the originals.

Because of this, though, I think I should probably do a 1.7.0-1
release. Just kidding. A 1.7.1 release to fix the Guice dependency and
get the redeployed copies right the first time. There are likely some
local repos out there that already downloaded the bad RC2 files. But
I'll wait a bit and see if anything else shows up that snuck through
the RC phase before doing so.

Please let me know if anyone finds any other issues.

Thanks.

Bill

[Chee Seng Chua]

Hi all, 

Sorry about not marking the Guice as optional, I should have done so when upgrading the TestNG version.

Best Regards,

Chee Seng

[Bill Venners]

Hi All,

No worries Chee Seng. It's fixable. Unfortunately it looks like the
bad jar files made it up to Maven central, though, so 1.7 is toast.
Hopefully the copied jars on Maven central will get updated at some
point, but clearly we need a clean release. I'll do a 1.7.1 release
tomorrow. It takes most of the morning, but I should have it out by
noon.

I also noticed just now that Google Groups had for some reason not
been notifying me of new pending posts to this group since Jan 20, so
there were five in there just now. I approved all of them, but only
three came through so far. One by Sean Parsons about a problem with
Scala 2.10 was dropped, and an earlier post one by Muki on custom
matchers. Neither of these is accessible from the pending messages
anymore, so if they don't come through later, they are lost so you may
want to repost from the copy in your outbox.

Bill