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

["Hudson (JIRA)" <ji...@apache.org>]

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

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

Integrated in tapestry-5.2-freestyle #285 (See [https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/285/])
    TAP5-116: Configure the inputs and outputs of generateGrammarSource task, to prevent unnecessary execution
TAP5-116: Fix odd line ending issue exposed by switch from Maven to Gradle

Still don't know why the change made a difference
TAP5-116: Set up a large heap size and PermGen space for tests across all projects
TAP5-116: Add note about potential problem with path names and spaces
TAP5-116: Ignore the bin/ folder (output folder for Eclipse .classpath files generated by Gradle)
TAP5-116: Replace Maven build with Gradle build

Get tapestry-core to build Antlr sources and compile them


> 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