tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-116) Replace Maven build with Gradle build
Date Fri, 01 Jul 2011 00:56:29 GMT

    [ https://issues.apache.org/jira/browse/TAP5-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058163#comment-13058163

Hudson commented on TAP5-116:

Integrated in tapestry-trunk-freestyle #400 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/400/])
    TAP5-116 - Removed fix for tapestry-ioc creates a dependency on tapestry-annotations instead
of tapestry5-annotations.

joshcanfield : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1141754
Files : 
* /tapestry/tapestry5/trunk/tapestry-ioc/build.gradle

> Replace Maven build with Gradle build
> -------------------------------------
>                 Key: TAP5-116
>                 URL: https://issues.apache.org/jira/browse/TAP5-116
>             Project: Tapestry 5
>          Issue Type: Task
>    Affects Versions: 5.3.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.3.0
> I like Maven dependency management.
> However, it is increasingly evident to me that the Maven approach to the actual build,
based on endless plugins and configurations, is not worthwhile.  The only part that's necessary
is the Maven Ant tasks, which encapsulate downloading dependencies, installing them, and deploying
them to remote repositories.
> Everything else worthwhile that Maven provides could be created as easily using Ant and
perhaps a few Velocity templates.  I'm willing to bet that the end result would work faster
and take far less effort to maintain.
> Gradle is the way to build Tapestry.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message