I don't know if it makes complete sense here, but creating an arquillian gradle container would simply a lot of these issues.
Sent from my iPhone On Aug 25, 2011, at 7:58, Luke Daley <[email protected]> wrote: > Hi, > > I am working on some bits around our integration testing fixtures and > thinking about what a publicly usable version of this might be like. > > Do you think we would want to allow people to execute Gradle in different > manners like we do? If I'm developing a plugin and want to integration test, > am I really going to want to test with the daemon, and embedded etc? > > Initially, I was inclined to think that we should *only* support testing > using a forking mode (daemon or not) but I guess users will want to have the > choice of making the same tradeoff that we do where we run embedded for speed > during development and trade off accuracy. > > I am not planning to do anything in this area soon, just formulating a bit of > an idea in my head how this might work while I'm in this area. > > -- > Luke Daley > Principal Engineer, Gradleware > http://gradleware.com > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
