specs dependencies

[walterc]

i am using sbt 0.6.7 with scala 2.8.0-beta1-rc3. when i tried to
include specs library (1.6.1-2.8.0.Beta1-RC3), i needed to include
some of its dependencies (ScalaTest, ScalaCheck, JUnit, Mockito)
before my tests compiled. i know specs had its dependencies marked
"optional" in its pom file. so if they are really optional, why do i
need include them? is this a specs thing or sbt thing?

[Mark Harrah]

I'd guess it is a specs thing without knowing more. I assume that you
aren't making use of the features that require those libraries in your
tests, but it might still help to see the problematic test code.

-Mark

> --
>
> You received this message because you are subscribed to the Google Groups
> "simple-build-tool" group.
> To post to this group, send email to simple-b...@googlegroups.com.
> To unsubscribe from this group, send email to
> simple-build-t...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/simple-build-tool?hl=en.
>
>
>

[walterc]

very simple code:

object SampleSpecification extends Specification {

"1 + 1 = 2" in {
1 + 1 must_== 2
}
}

On Dec 19, 11:53 pm, Mark Harrah <dmhar...@gmail.com> wrote:
> I'd guess it is a specs thing without knowing more.  I assume that you
> aren't making use of the features that require those libraries in your
> tests, but it might still help to see the problematic test code.
>
> -Mark
>

[Mark Harrah]

specs now defines org.spex.Specification in addition to
org.specs.Specification as test class superclasses. sbt has to tell
the compiler load this class in order to determine if there are any
subclasses of org.spex.Specification. This means the compiler has to
load JUnit classes and make junit not optional.

org.spex.Specification extends org.specs.Specification, so I'm not
sure why it is added explicitly. I think the solution is for specs
not to list org.spex.Specification for the test interface. Eric, does
this sound right?

Thanks,
Mark

On 12/19/09, walterc <wei...@gmail.com> wrote:

[etorreborre]

> I think the solution is for specs
> not to list org.spex.Specification for the test interface. Eric, does
> this sound right?

Yes, that makes sense Mark. I just redeployed a 1.6.2-SNAPSHOT version
fixing this.

Walter, could you check if it works for you?

Thanks to both of you,

Eric.

On Dec 20, 10:29 am, Mark Harrah <dmhar...@gmail.com> wrote:
> specs now defines org.spex.Specification in addition to
> org.specs.Specification as test class superclasses.  sbt has to tell
> the compiler load this class in order to determine if there are any
> subclasses of org.spex.Specification.  This means the compiler has to
> load JUnit classes and make junit not optional.
>
> org.spex.Specification extends org.specs.Specification, so I'm not
> sure why it is added explicitly.  I think the solution is for specs
> not to list org.spex.Specification for the test interface.  Eric, does
> this sound right?
>
> Thanks,
> Mark
>

[Walter Chang]

I would love to test it but I am using Scala 2.8.0.Beta1-RC3 right now...

--
.......__o
.......\<,
....( )/ ( )...

[etorreborre]

I redeployed a version of specs for Scala 2.8.0.Beta1-RC3 which should
fix the issue.

Thanks for trying it and telling me if it works.

E.

> > For more options, visit this group athttp://groups.google.com/group/simple-build-tool?hl=en.

[Walter Chang]

i am sorry but i am not able to locate jar file. i couldn't find it
in the scala-tools snapshots repo nor the nexus.scala-tools.org repo.

[etorreborre]

You should see it here:
http://nexus.scala-tools.org/content/repositories/releases/org/scala-tools/testing/specs/1.6.1-2.8.0.Beta1-RC3.

[Walter Chang]

thanks, it works now.