I second. Maven usually works as advertised. In fact, one of the reasons I considered Tapestry superior to some other web frameworks is that it integrates with Maven, and tutorials provided archetypes for a quick start.
Maven is far from perfect, but it is the best out there if you use continuous integration and such. On Wed, Jun 17, 2009 at 2:31 PM, Geoffrey Wiseman < geoffrey.wise...@gmail.com> wrote: > On Wed, Jun 17, 2009 at 1:21 PM, Norman Franke <nor...@myasd.com> wrote: > > > Chapter 2 just plain didn't work for me. I think part of it is due to > Maven > > generally being extremely fragile and working less than half of the time. > > However, even after working around that, you can't just import the > project > > into Eclipse. At least not under Eclipse 3.4.2. > > > > Weird. Maven has a lot of issues, IMO, but working less than half the time > doesn't tend to be one of them for me. And certainly the project generated > by eclipse:eclipse imports fine into Eclipse 3.4.2 for me, which I've done > in countless projects, including a few with Tapestry. Maybe if we had > specifics here we could help to diagnose. > > - Geoffrey > -- > Geoffrey Wiseman > http://www.geoffreywiseman.ca/ >
