On Sunday, October 17, 2010, at 01:48 pm, Dierk König wrote: > The idea would be that executing the tests would not be any different. > Same gradle call, same dependencies.
I am not sure what you mean by "same gradle call, same dependencies" here. However, this did open my eyes to another possibility (or maybe this is what you meant)... In Gradle you could set it up so that building the main module forced an execution of the testsuite module as well. That opens up some possibilities not available in Maven. One main difficulty with Hibernate in regards to its testsuite is the fact that we need to run that numerous times (against different databases on varying jvms) in the CI case. You'd really prefer the module itself to get built, installed and uploaded just once during this process. Moving testsuite to a separate module made that easier. I started investigating writing a plugin for Gradle to allow iteration through a set of tests with different "set ups". I think I'll need to dust that code off and finish it up now. --- Steve Ebersole <[email protected]> http://hibernate.org --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
