You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2011/04/01 02:02:06 UTC

[jira] [Commented] (TAP5-116) Replace Maven build with Gradle build

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

Hudson commented on TAP5-116:
-----------------------------

Integrated in tapestry-5.2-freestyle #300 (See [https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/300/])
    TAP5-116: Set up test compile and runtime classpaths to include the provided configuration


> 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
>
> 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