Re: [scalatest-users] Re: Version naming question

Hi Kevin,

I think I can answer my own question. Each version gets a pom that
specifies its dependencies, and these two different jar files have two
different scala library dependencies. Plain old scalatest-1.0-SNAPSHOT
depends on 2.7.3 or so, and scalatest-1.0-for-scala-2.8.0-SNAPSHOT
depends on a snapshot build of the 2.8 scala-library.jar. So these
really need to be either different versions of the same artifact, or
different artifacts of the same group. We ended up making them
different versions of the same artifact, but sbt defaults to making
them different artifacts of the same group apparently. The jdk1.4 and
jdk1.5 examples in the Maven documentation may be different because
you don't specify a jdk as a dependency. They kind of assume you're
using some jdk to use Maven.

Bill

On Fri, Aug 21, 2009 at 2:37 PM, Bill Venners wrote:
> Hi Kevin,
>
> The Maven repository will be one way of grabbing it, but you'll also
> be able to grab a zip file off the scalatest home page. It does look
> like classifier was intended for this. That would put all these files
> in the same 1.0-SNAPSHOT directory for the scalatest artifact:
>
> scalatest-1.0-SNAPSHOT-for-scala-2.8.0-sources.jar
> scalatest-1.0-SNAPSHOT-for-scala-2.8.0.jar
>
> scalatest-1.0-SNAPSHOT-javadoc.jar
> scalatest-1.0-SNAPSHOT-scaladoc.jar
> scalatest-1.0-SNAPSHOT-sources.jar
> scalatest-1.0-SNAPSHOT.jar
>
> In this case the scaladoc and javadoc are the same for both, but the
> source is slightly different. I wonder if the reason the sbt guys
> didn't go this route is they didn't want people to end up downloading
> more jars than they really needed. Josh, I vaguely remember a
> conversation about this, maybe on scala-tools mailing list, but I
> can't find it. Can you summarize the reasoning for sbt going with the
> approach it did?
>
> Thanks.
>
> Bill
>
> On Fri, Aug 21, 2009 at 12:11 PM, Kevin
> Wright wrote:
>> If we're going with maven as the deployment mechanism, isn't this a clasic
>> use-case for using a classifier?
>> http://maven.apache.org/pom.html#Dependencies
>> http://maven.apache.org/ref/2.1.0/maven-model/maven.html#class_dependency
>>
>>
>>
>> On Fri, Aug 21, 2009 at 8:06 PM, Bill Venners wrote:
>>>
>>> Hi Josh,
>>> Darn. One hour too late. I deployed under the scalatest artifact ID with
>>> the name scalatest-1.0-for-scala-2.8.0-SNAPSHOT.jar. Can you elaborate on
>>> why this is better as two artifacts? It is essentially the same release
>>> compiled for two scala versions (or point me to the mailing list discussion
>>> if it was on a mailing list.)
>>>
>>> Thanks.
>>> Bill
>>> ----
>>> Bill Venners
>>> Artima, Inc.
>>> http://www.artima.com
>>> On Aug 21, 2009, at 11:49 AM, Josh Suereth
>>> wrote:
>>>
>>> SBT takes the convention....
>>>
>>> groupId: org.scalatest
>>> artifactId: scalatest_2.8.0-SNAPTHOST
>>> version: 1.0-SNAPSHOT
>>>
>>> We had a lot of discussion about this decision, and we feel it's the best
>>> way to integrate with the existing Maven Repository structure and still
>>> allow per-scala versions of libraries along with integration.   When you're
>>> talking a single jar file, I'm not sure what I'd prefer (as I usually
>>> declare dependencies now)
>>>
>>> - Josh
>>>
>>> On Thu, Aug 20, 2009 at 8:23 PM, Bill Venners wrote:
>>>>
>>>> Hi All,
>>>>
>>>> Several people have asked me for a snapshot of ScalaTest 1.0 that
>>>> works with Scala 2.8. I got it compiling today, but now I'm faced with
>>>> naming these two different versions. I have in the past noticed that
>>>> because of binary compatibility problems that often show up from one
>>>> release to the next of Scala, at least major releases, I feel the need
>>>> to name a Scala version in a Scala library Jar more than was the case
>>>> for Java.  I'm thinking of calling them:
>>>>
>>>> scalatest-1.0-for-scala-2.7-SNAPSHOT.jar
>>>>
>>>> and
>>>>
>>>> scalatest-1.0-for-scala-2.8-SNAPSHOT.jar
>>>>
>>>> The problem there is there was no 2.7 or 2.8 release, there's always a
>>>> third number. I could say 2.7.x and 2.8.x, but in truth I'm not sure
>>>> if the latest ScalaTest works on 2.7.2 and under. It does work on
>>>> 2.7.3 through 2.7.5, so maybe I should say 2.7.3 and 2.8.0.
>>>>
>>>> Any opinions or suggestions?
>>>>
>>>> Thanks.
>>>>
>>>> Bill
>>>> ----
>>>> Bill Venners
>>>> Artima, Inc.
>>>> http://www.artima.com
>>>
>>>
>>>
>>
>>
>> --~--~---------~--~----~------------~-------~--~----~
>> You received this message because you are subscribed to the Google
>> Groups "scalatest-users" group.
>> To post to this group, send email to scalatest-users@googlegroups.com
>> To unsubscribe from this group, send email to
>> scalatest-users+unsubscribe@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
> Artima, Inc.
> http://www.artima.com
>