[
https://issues.apache.org/jira/browse/TAP5-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053012#comment-13053012
]
Hudson commented on TAP5-116:
-----------------------------
Integrated in tapestry-trunk-freestyle #376 (See
[https://builds.apache.org/job/tapestry-trunk-freestyle/376/])
TAP5-116: tapestry-core should not exclude build/generated-sources
TAP5-116: Idea plugin used wrong java version. Regenerating idea project caused
duplicate modules
joshcanfield :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1138269
Files :
* /tapestry/tapestry5/trunk/tapestry-core/build.gradle
joshcanfield :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1138268
Files :
* /tapestry/tapestry5/trunk/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
>
> 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
