[rules-dev] Dropping Maven for Gradle?

[Geoffrey De Smet]

I don't know of any enterprise size build that uses Gradle or another 
one of those frameworks that:
- no serious projects uses
- no one knows how to configure advanced stuff
- doesn't integrate with hudson, nexus, eclipse, intellij and netbeans
- but looks really cool.

That being said, you do have a really valid point that our build could 
use some care:
- we violate a lot of maven best practices
-- use of <repository> tag
-- compile dependencies VS transitive depedencies
-- depdencyManagement for all versions in the parent pom
-- guvnor's generated files are not all in target directory
-- the eclipse plugin should be build with maven tycho
-- drools-examples should build in the main build
-- there must not be jars in subversion
I'd love to clean it up, but I have no time atm.

And there's also some good things coming our way:
- Maven 3 is coming very soon (twitter jason: "Maven 3.0-beta-1: 1 issue 
remaining Apr 9th")
- and it's huge leap forward (twitter ceki: "Started building logback 
using maven 3. With mvnsh, the "mvn compile site" command which took 8 
seconds now takes less than 1 second. Cool.")
- Jboss will upgrade to a nexus professional repository (tommorrow I think)


With kind regards,
Geoffrey De Smet


tolitius schreef:
> Just wondering if any of the devs considered to use something a bit more
> efficient for the whole Drools Suite build. Maven is really painful,
> especially for huge source bases with cross dependencies like drools... 
> 
> Ivy? Gradle? Buildr?
> 
> /Anatoly