Re: 4.1.2 without maven

2007-06-05 Thread Daniel Jue
When I came to this point a few weeks ago, taking on an unfamiliar build tool (maven) seemed like such a pain, just because I wanted to work with 4.1.2. There were lots of emails and notes online that i had to search through to overcome little problems I had. But in the end, it was worth it. I

Re: 4.1.2 without maven

2007-06-05 Thread Chris Chiappone
I don't believe that its out yet so maven is the way to go. What I actually do since our project does not use maven is set up a separate project with maven just for tapestry and its dependencies and then copy over the appropriate jar files. Seems to work for me. Just make sure you have the rig