[ 
https://issues.apache.org/jira/browse/TAPESTRY-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575674#action_12575674
 ] 

Michael Gerzabek commented on TAPESTRY-1732:
--------------------------------------------

I honestly was impressed how easy it was to setup a project without reading 
more than a couple of sentences from the documentation website tutorial 
(Chapter 2: Your First Tapestry Application): mvn archetype:create and mvn 
jetty:run. Really awesome compared to many other ASF/ other OSS projects!

I didn't know anything about maven then. So while getting on the road with T5 I 
also learned to honor the powerful dependency management maven can do. And most 
important. My CVS/ SVN is light in sense of MB used by libraries copied into 
each and any project like our company did a few years ago.

I also realized that when I have a growing project - e.g. using axis2 now - the 
management seems to get a little more complex to eclipse (using 3.3 Europa). I 
sometimes now switch off the build automagically option to get away from 
waiting for the n th resolution of my build path.

I personally would keep tapestry mavenized. But I could imagine that with a few 
goals (don't know if that's the right term) one ant file and the eclipse/ IDE 
files could be generated and then in eclipse the maven plugin would not be 
needed.


> Replace Maven build with Ant build
> ----------------------------------
>
>                 Key: TAPESTRY-1732
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1732
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 5.0.5
>            Reporter: Howard M. Lewis Ship
>             Fix For: 5.1
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to