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 have since moved on to T5 using maven as my dependency monkey.
I also had to manually add some non-tapestry-required jars to my local repository, since the most recent versions were not in the repositories I knew of. There is a special maven command line flag for eclipse wtp users, so search for that if you need it. Another tip for eclipse users is to add an M2_REPO classpath variable to point at your local repository, i.e. C:/Documents and Settings/philton/.m2/repository This is under Window->Preferences->Java->BuildPath->Classpath Variables FWIW, I am staying away from the plugin for maven that runs in Eclipse. It messes up my POM. I just use maven via command line, and there is an eclipse plugin that can be invoked there. I'm now the only person at my company that knows maven, although I am just starting. So that feels good! =) On 6/5/07, Paul Stanton <[EMAIL PROTECTED]> wrote:
just downloaded the latest framework, contrib and annotation jars hoping they would work with the libs I already have for 4.1.1 they don't where can I get the project .zip or something to list the required libs and their versions? Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
