[jira] Commented: (BUILDR-332) New maven location for scalatest 1.0 not configurable

["Alex Boisvert (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BUILDR-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12775188#action_12775188 ] 

Alex Boisvert commented on BUILDR-332:
--------------------------------------

By the way, in Buildr 1.3.5, this issue can be fixed by monkey-patching the ScalaTest class in your Buildfile:

module Buildr::Scala
  class ScalaTest
    class << self
      def dependencies
        ["org.scalatest:scalatest:jar:1.0"] + Check.dependencies +
          JMock.dependencies + JUnit.dependencies
      end
    end
  end
end

We've now upgraded to ScalaTest 1.0 in trunk so Buidlr 1.4.0 will use it by default.

*BUT* even with this fix (your patch or the change in trunk) there's another issue about supporting both ScalaTest 0.9.5 and 1.0 which is that the integration code requires some additional tweaking for ScalaTest 1.0.  I've also fixed this in Buildr trunk (a simple change of regex) but I'm hoping to improve the code so that we don't have to parse the ScalaTest report output to determine the pass/fail/ignored tests.

> New maven location for scalatest 1.0 not configurable
> -----------------------------------------------------
>
>                 Key: BUILDR-332
>                 URL: https://issues.apache.org/jira/browse/BUILDR-332
>             Project: Buildr
>          Issue Type: Bug
>          Components: Test frameworks
>    Affects Versions: 1.3.5
>         Environment: All
>            Reporter: Alex Eagle
>            Assignee: Alex Boisvert
>         Attachments: BUILDR-332.patch
>
>
> At revision 829438, vim +63 lib/buildr/scala/tests.rb
> ["org.scala-tools.testing:scalatest:jar:#{version}"] + Check.dependencies +
> The new version 1.0 of scalatest has been released, and the maven package has changed. Now it is here:
> http://www.scala-tools.org/repo-releases/org/scalatest/scalatest/1.0/
> Need some conditional here to look in the right package depending on the requested version.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.