On 6/13/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Hmmmmmm... Sounds like a major usability issue. Maven in general is very easy to use, so if dependency resolution isn't happening right something is potentially broken or not documented properly?
I wouldn't really agree on this one... Maven is IMO not that easy to use. I believe the two jars required are for hibernate, and they are probably not available in Maven repositories because of legal issues (one of them was jta.jar and I can't remember the other one). And things are properly documented, the error messages were very clear but I don't have the maven command line version installed so it makes the process quite cumbersome. I just don't like having command line tools to build projects because most of the time, this means that you need to configure the command line tools + the eclipse project. Normally I wouldn't be so vocal about things but I think tapernate is really
crucial/has lots of potential to do a lot of good for tapestry, it would be a shame if minor usability issues were keeping it back ;)
James is doing a great job, the only small thing missing for tapernate are IMO a home page with straightforward links for jars. Thanks, Henri.
