On Wed, Oct 22, 2008 at 7:06 AM, Tammo van Lessen <[EMAIL PROTECTED]>wrote:
> 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? What looks cumbersome about them? The long list of dependencies? > > b) although a "buildr package" compiles and packages the extensions as > expected, it does not run the tests. This looks like a bug, even running "buildr ode-extensions:test" from the root doesn't run anything. > > c) buildr eclipse does not create .project files when run in trunk/. > If run in trunk/extensions it works. > Might be related to b). Matthieu > > a) and b) are IMO the more important things, do you have any ideas? > > Thanks, > Tammo >
