buildr-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Boisvert <>
Subject Re: Sub-projects and dependencies
Date Wed, 14 Sep 2011 13:31:11 GMT
Hi Marc-André,

The failing tests are probably due to your code depending on the current
working directory being the same as before.  Buildr does not change the cwd
during test execution so you probably have to, e.g., load files through the
classpath instead, or adjust your code accordingly.

Other than that, subprojects should only recompile and be tested if there
have been changes.  Not sure what's going on without more detail, you may
want to run buildr in trace/verbose mode to see why it thinks there have
been changes.


2011/9/13 Marc-André Laverdière <>

> Hello everyone,
> I'm breaking one of my projects into subprojects and I'm getting some
> trouble.
> so I have
> core:
> crypto: core + own dependencies + core's dependencies
> io: core + crypto + their dependencies + own dependencies
> app: core + crypto+io + all their deps + own deps
> Now, some weird stuff happens...
> If I try to build io or app, I'll have crypto rebuilt and crypto's
> tests being run too.
> Even more interesting, if I got to crypto and run buildr test, the
> tests are successful
> But if I go to app and run buildr test, then crypto's test is run and it
> fails.
> FYI, I'm using Buildr 1.4.6 and ruby 1.8.7 (2011-06-30 patchlevel 352)
> --
> "Perseverance must finish its work so that you may be mature and complete,
> not lacking anything." -James 1:4

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