[ANN] Gradle 0.3 is released

[hdockter]

Hi,

we are pleased to announce the release of Gradle 0.3, a Groovy based  
build system.

To learn more see: www.gradle.org

Here is a summary of the most interesting new features and improvements:

- Gradle provides now a separate JDK 1.4. compatible distributions.
- We have improved the handling and naming conventions for archive  
tasks. See user's guide (UG) 9.7.3.
- The War plugin is now much more flexible regarding library  
handling. Gradle provides now a provided configuration to add  
libraries that should be used for compile and testing, but should not  
be bundled with the war. See UG 11.
- After going through a lot of pain with the windows start scripts we  
have decided to get rid of them and replace them with exe commands  
generated by launch4j. Thanks to Adam Pohorecki for contributing the  
foundations for this.
- To improve the responsiveness of Gradle the compiled build and  
settings files are now cached. For how to control the cache, see UG 4.6.
- Every task action has now access to the graph of the tasks to be  
executed. See UG 2.10.
- The wrapper task is now much more configurable regarding where the  
involved files are stored. See UG 16.
- We have started to implement a listener framework around the Gradle  
lifecycle. You can now register for example an afterEvaluateListener  
with a project which gets called after a project's build script is  
evaluated. For an example see UG 14.2.3.
- The Test task generates now JUnit HTML reports.
- Gradle enables now to execute tasks via their absolute path. See UG  
14.4.
- You can now define default tasks. See UG 2.9.
- You can define now global exclude for dependencies. See UG 12.2.6.
- Due to Groovydoc problems, we were not able to provided reasonable  
API doc in the past. This has changed now. For a big part of our  
public API we provide now Javadoc. With the release of 0.4 we will be  
able to provide this for all our API.

For our roadmap see: http://gradle.org/roadmap.html

Cheers,

- Hans

--
Hans Dockter
Gradle Project lead
http://www.gradle.org



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Jochen Theodorou]

Hans,

this sounds great

Hans Dockter schrieb:

> Hi,
>
> we are pleased to announce the release of Gradle 0.3, a Groovy based
> build system.
>
> To learn more see: www.gradle.org
>
> Here is a summary of the most interesting new features and improvements:
>
> - Gradle provides now a separate JDK 1.4. compatible distributions.
> - We have improved the handling and naming conventions for archive
> tasks. See user's guide (UG) 9.7.3.
> - The War plugin is now much more flexible regarding library handling.
> Gradle provides now a provided configuration to add libraries that
> should be used for compile and testing, but should not be bundled with
> the war. See UG 11.
> - After going through a lot of pain with the windows start scripts we
> have decided to get rid of them and replace them with exe commands
> generated by launch4j. Thanks to Adam Pohorecki for contributing the
> foundations for this.
> - To improve the responsiveness of Gradle the compiled build and
> settings files are now cached. For how to control the cache, see UG 4.6.
> - Every task action has now access to the graph of the tasks to be
> executed. See UG 2.10.
> - The wrapper task is now much more configurable regarding where the
> involved files are stored. See UG 16.
> - We have started to implement a listener framework around the Gradle
> lifecycle. You can now register for example an afterEvaluateListener
> with a project which gets called after a project's build script is
> evaluated. For an example see UG 14.2.3.
> - The Test task generates now JUnit HTML reports.
> - Gradle enables now to execute tasks via their absolute path. See UG 14.4.
> - You can now define default tasks. See UG 2.9.
> - You can define now global exclude for dependencies. See UG 12.2.6.
> - Due to Groovydoc problems, we were not able to provided reasonable API
> doc in the past. This has changed now. For a big part of our public API
> we provide now Javadoc. With the release of 0.4 we will be able to
> provide this for all our API.
>
> For our roadmap see: http://gradle.org/roadmap.html
>
> Cheers,
>
> - Hans
>
> --
> Hans Dockter
> Gradle Project lead
> http://www.gradle.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>

--
Jochen "blackdrag" Theodorou
The Groovy Project Tech Lead (http://groovy.codehaus.org)
http://blackdragsview.blogspot.com/
http://www.g2one.com/

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Helmut Denk]

after studying the gradle-usersguide, it seems clear to me, that
it's much better to join this effort, than to do proprietary
build-system-stuff or struggle with maven.

gradle implements a consistent bunch of very smart concepts.
this is a new-generation build-system. cool stuff. check it out !