On Tue, 03 Dec 2013 15:04:27 -0200, Norman Franke <nor...@myasd.com> wrote:
Same here. I mostly do, but not really. Maven seems to work great except
when it doesn't. Then I spend a half a day fixing it. So I just stopped
using it. My templates and java files locations are compatible with the
plugin, but the css and js files aren't.
But, using Maven or not, I still think its source folder organization is
the best and I recommend it. The Tapestry project itself used Maven, now
uses Gradle, but still uses the Maven folder organization. Gradle uses the
Maven folder organization by default:
http://www.gradle.org/docs/current/userguide/java_plugin.html#N1206F
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
Help me spend a whole month working on Tapestry bug fixes and
improvements: http://igg.me/at/t5month
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
