This is probably my last post of the day. As I discussed with Hans,
Luke, and Adam before, abuild has a really thorough test suite, and I
would love to be able to have gradle's C++ support benefit from the test
cases. I'm not sure what the best way to do this is or when the time
would be right. I think gradle's C++ support isn't yet advanced enough
to be able to pass most of the tests, and if done right, many of the
tests would have to be changed a little, particularly if gradle uses
digest-based dependencies instead of modification-time-based
dependencies. Besides, the directory structure, platform stuff, and
lots of other details will be different. Abuild has many hundreds of
test cases, but only a fraction of them are actually related to C and
C++ support. Probably at some point it would make sense for someone to
go through abuild's test suite, steal test ideas from it, and
re-implement those tests with gradle. I don't know whether I'd ever
have time to do that or when gradle would be ready. For now, I'll just
mention that this is a potential resource for gradle's testing and that,
when the time is right, if I don't have time to contribute in this way
directly, I would happily walk someone through abuild's test suite, help
figure out which tests are appropriate, etc.
--Jay
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
