On Oct 8, 2008, at 2:21 PM, Jason Dillon wrote:

Single project build does not mean simple build. The gradle build is so far a single project build. Nonetheless it has the build script plus 15 classes for expressing the build logic. You don't want to put the content of 15 classes in a pom.xml, do you? I'm slightly annoyed by your constant claim that I have a lack of basic understanding in regard to Maven or tell something about Maven which is factual untrue. There hasn't been a single issue were you could prove this (except the naming of the enforcer plugin ;)). I have been the build master for very complex Maven builds. I know what I'm talking about. For example for me it is also a bizarre level of indirection if I need 20 lines of XML to call a simple ant task. May be you call this straight forward. Fair enough. We interpret things differently. This disagreement does not mean that you or me does not know how Maven works.

My point is that you can't model with Maven an arbitrary deep acyclic graph.

<snip>

I think this is very important. I think it is crucial for Gradle to play very nice with Ant and Maven. In regard to repositories, in regard to reusing a pom.xml (at the moment we have a script that transforms the dependency notations from Maven to Gradle). Of course using plugins is also very important. But there are issues. For example in the last Maven build I have been responsible for, we have written a plugin that took a pom object as an argument to do some advanced dependency filtering for creating bundles. I'm skeptical if it would work out to mock Maven objects in Gradle here. But I guess for many plugins this wouldn't be an issue.

<snip>

We had some email exchange in the old days when we both were involved with JBoss for a while and you were the cvs master there. I remember you were writing about your jet lag from just having arrived in Bangkok. Who knows, there might be demand for a Gradle training there :)

<snip>

- Hans