buildr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Victor Hugo Borja" <>
Subject Re: Replacing VERSION/REQUIRES with version/dependencies and using YAML files to pick versions of specific libraries
Date Wed, 17 Sep 2008 06:57:56 GMT

On Tue, Sep 16, 2008 at 7:26 PM, Assaf Arkin <> wrote:

> There's no official API, but by convention you can get the version
> number from Ant.version (was: Ant::VERSION) and the list of
> dependencies from Ant.dependencies (was: Ant::REQUIRES).  These
> methods are there in case the truly motivated need to mess with them,
> maybe pick a random version of JUnit on each build, or replace JMock
> with JSerious.

We will need to document on modules having a dependencies method, the key
users can use in the yaml file. I like having
   ant: 1.7
but I'd also like something more qualified (and more rubyish..) like
   Buildr::Ant::version: 1
some modules may need different versions for the same artifact.

How could we handle cases like setting a fixed JUnit/TestNG version for
JtestR  to use.
Currently JtestR simply includes TestNG.dependencies, would this case
require the user
to override JtestR::dependencies ?

Another interesting case[1] is how to set the dependencies or versions
per project. Say a project needs a particular JMock or XMLBeans version.

I'm putting this first on Github for everyone to review, check, comment:

Great, I really like these reorg changes.

I've rebased my JtestR branch to use your changes, and
changed it not to use REQUIRES constant.

> The official issue is 148 (configure JUnit from YAML file), also
> related to 140 (get rid of const_defined?), 115/138 (broken
> repositories.local = )
> [1]


Quaerendo invenietis.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message