On Thu, Aug 25, 2011 at 11:49, Luke Daley <[email protected]> wrote:
> > On 25/08/2011, at 6:20 PM, Jason Porter wrote: > > > On Aug 25, 2011, at 10:59, Luke Daley <[email protected]> wrote: > > > >> > >> On 25/08/2011, at 4:52 PM, Jason Porter wrote: > >> > >>> I don't know if it makes complete sense here, but creating an > arquillian gradle container would simply a lot of these issues. > >> > >> This seems very focussed on J2EE, or am I misreading it? > > > > It spawned from Java EE, yes, but it's not directly tied to it. > > > >> On first glance I am not quite sure how this fits. Can you elaborate? > > > > Arquillian is a framework at it's core for running tests within a > container, where a container is any sort of environment that isn't standard > Java SE, something you get just for executing "java". Gradle is essentially > a container for running specialized groovy scripts. > > > > Those may be somewhat loose definitions, but Arquillian could start a > Gradle instance — embedded, forked, daemon and "deploy" a Gradle script to > test. > > Right, that makes sense. > > What kind of issues does it solve though? All of the infrastructure is taken care of for starting / stopping the container, allowing for forks, returning test results, expecting failure. Just a thought about a solution that would allow flexibility for gradle users testing plugins. > -- > Luke Daley > Principal Engineer, Gradleware > http://gradleware.com > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Jason Porter http://lightguard-jp.blogspot.com http://twitter.com/lightguardjp Software Engineer Open Source Advocate Author of Seam Catch - Next Generation Java Exception Handling PGP key id: 926CCFF5 PGP key available at: keyserver.net, pgp.mit.edu
