On Jun 17, 2009, at 2:31 PM, Geoffrey Wiseman 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.
Once you get it working for a project, it generally works. It's the
starting of new projects where problems arise. I've had to purge
my .m2 directly countless times. Just yesterday, while adding
tapestry5-acegi support, Maven decided to use Tapestry 5.1.0.5 with
Tapestry Annotations 5.0.x, leading to all sorts of problems. I had to
move the dependancy for Tapestry 5 first in the pom.xml, and that
fixed it. At least it works now.
While trying appfuse, I was never able to get Maven to build a
project. Random errors about missing this or that. From googling, it
seems a major problem with Maven is that your build environment is now
dependent on rules on potentially dozens of other sites. This makes
reproducibility nearly impossible. One slight typo and no one can
build. I think this is a major hit to developer productivity. Sort of,
"gee, it worked last week and I didn't touch anything." That's just
not acceptable, IMHO. But, it's popular and mostly works, so I have no
problems using it.
I don't think the tutorial said to run mvn eclipse:eclipse either,
just import it into eclipse. That fails.
-Norman
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
