Re: [rules-dev] Dropping Maven for Gradle?

@Mark, @ge0ffrey, Cool, that is good news. A least splitting this humongous build tree would be immediately useful. As far, as the argument that no one uses Gradle or IVY, I completely disagree: 1. I have worked on at least (from what I can recall) 4 enterprise [quite large] clients that used IVY, and let me tell you, build teams were extremely fast efficient, compare to Maven madness I usually see. 2. "no serious projects uses", well, how is Spring Framework for a serious project? Spring 3.0 uses IVY. I understand you may no find all the dynamic languages serious [ I call in an "enterprise fear" :) ], but Grails uses Gradle, as well as Spock, and many others. 3. IVY Hudson plugin: http://wiki.hudson-ci.org/display/HUDSON/Ivy+Plugin Gradle Hudson plugin: http://wiki.hudson-ci.org/display/HUDSON/Gradle+Plugin 4. "no one knows how to configure advanced stuff", "nobody uses it, etc..". well 10 years ago nobody would use Spring ( or Seam, just to be closer to JBoss hearts here :) ), everybody used EJB2, right? You get my drift.. 5. Looked at Nexus Repo + Maven 3, listened to Jason van Zyl on a couple of conferences... Seems... ok, but a bit too complicated, but I guess, if JBoss goes this direction, Drools has no choice in a matter.. /Anatoly -- View this message in context: http://n3.nabble.com/Dropping-Maven-for-Gradle-tp727052p728300.html Sent from the Drools - Dev mailing list archive at Nabble.com.