Hi guys,

I'm currently tidying the extensions a bit and stumbled upon a problem
with Buildr of which I'm currently too stupid to solve ;)

The idea of the current setting was to have an extension zoo within
trunk, the "extensions" directory. This directory contains the extension
modules (currently e4x and jms event listener). They should be bundled
independently of the main distribution as they may have their own
dependencies. This works already almost as expected, but:

  a) the nested buildr projects look IMO a bit cumbersome, is there an
easier way to do it?
  b) although a "buildr package" compiles and packages the extensions as
expected, it does not run the tests.
  c) buildr eclipse does not create .project files when run in trunk/.
If run in trunk/extensions it works.

a) and b) are IMO the more important things, do you have any ideas?

Thanks,
  Tammo

Reply via email to