consider using gradle for the build

[GoogleCodeExporter]

consider using gradle, a groovy/dsl-based 
build-framework, as a replacement for maven.
gradle has some very smart concepts and is
much easier to handle compared to maven.

as gradle is maven-compatible there should
not be much work to do besides adding a 
'build.gradle'.

Original issue reported on code.google.com by fanny.ae...@gmx.de on 21 Nov 2008 at 4:42

[GoogleCodeExporter]

this should have been an 'improvement'-issue not
a 'defect'-issue. sorry.  

Original comment by fanny.ae...@gmx.de on 21 Nov 2008 at 4:44

[GoogleCodeExporter]

here is a snippet for 'build.gradle':

usePlugin('groovy')

sourceCompatibility = 1.5
targetCompatibility = 1.5
group = 'org.gmock'
version = '0.3'

dependencies {
    addMavenRepo()
    compile "org.codehaus.groovy:groovy:all-1.5.6"
    compile "org.hamcrest:hamcrest-core:1.1"
    compile "org.hamcrest:hamcrest-library:1.1"

    # should better be testCompile ?
    # but there is dependency to junit in src/main
    compile "junit:junit:4.4"
}

consider using 'Flat Directory Resolver' instead of
MavenRepo @see Gradle-Users-Guide 12.5.3

Original comment by fanny.ae...@gmx.de on 21 Nov 2008 at 5:14

[GoogleCodeExporter]

Thanks for the suggestion, gradle seems an interesting projects.

At the moment we are doing a little use of Maven and it's doing the job pretty 
well.
So I can't see a reason to change for anything else.

Maven is now see as a standard in the industrie, it even come preinstall in 
macos
now. This mean that anyone with maven knowledge will know how to generate the 
gmock
package.

We are quite busy with our future release and won't be spending time on it at 
the moment.

Original comment by julien.g...@gmail.com on 21 Nov 2008 at 8:14

• Changed state: WontFix

[GoogleCodeExporter]

ok i understand that.

you can stay with maven and offer 
build.gradle for nearly no extra-costs.

both gradle and gmock have bright prospects 
IMO ... good luck. 

Original comment by fanny.ae...@gmx.de on 22 Nov 2008 at 11:56

[GoogleCodeExporter]

I had read the gradle user guide before, and it is an interesting project.

But, as Julien said, Maven is enough for us. And besides the reasons Julien 
mentioned, m2eclipse is providing a great gui to edit pom.xml, which makes it 
very 
easy, so the simple dsl which gradle provides cannot persuade me to change our 
build 
system, at least in this project.

Original comment by JohnnyJianHY on 22 Nov 2008 at 1:33