Hello, Ok, seems removing \"wicket-velocity-1.3.0-beta3.jar\" from build path solved problem with velocity problem. But please explain me why removing package from build path solves the problem if nowhere in my Hello World code i call for any of the velocity packages. Is there some duplicities in packages or what?
As to Maven2. It seems that like you in some way force developers to Maven2. :-) In wicket inAction EA there is just mentioned that when using Ant you need to do some work about libraries ant Maven manages it for you. This is too little for serious docs. Please do look into Icefaces free docs. There is steb by step mentioned what libs one need to enable which feature and the libs are added as demo app more feature ritch. Developer needs to understand core functionalities and dependencies. Just After understandig this developer is able to set up Ant project, make project, Eclipse or Netbeans based project and if you want also Maven. :-) But many of the advices about libs was \"Use Maven2\" like. If you use it, so use it but do not force me to use it. Explain in some part od book or docs what do I need to run which part of wicket to save my time to go into jars and solve dependencies troubles. Yes Maven solves you some problems with dependecies and also si suitable for small pr oject but at big projects it definitely fails. :-/ So please. I know you have lot of work with wicket, and as users can see you have a good aproach. But please do spend some time to at least write one chapter about libraries, neede dependencies and so on. If you have licensing problems just make one clear site with core libs link, dep libs link and explanation what feature they are enabling and so on. And make some quick start page in which you explainn dependecies on simple sample app :-)Do not take alibistic aproach of hiding everithing besides Maven. :-) Off topic section: We use Maven for more than one year, also Maven2, in the begining there was some WoW`s about how Maven Manages project. Really great. But as the project continued and wee needed to add many not so standard feature to project, like advanced autorization, very non standard libraries we were forced in the troubles wchich could be avoided when there was no Maven2. also the project layout is not the best for our taste. IMHO of cource. Rewriting project build to ANT took us 6 days, but from that time we saved us a lot of time and nerves of solving Maven troubles. From that time we just developed, exactly what we were paid for. Idea of Maven2 is very nice and usefull, but implementation is kind of tragedy :-/. If I would Alayster Crowley I`d like Maven. Because its black magic, but I`m just dump developer who is not even to able to hypnotize someone :-)). as we talked about Ant and Maven2 we really realized the good sides of Maven. but Ant has simple basic idea with few bilding bloc ks, which when you combine them wiselly works perfectly. YOU do no need to study Ant. Just use it. In Maven wee need to study Maven, Study black Magic without success. :-) It remainds me of one Joke. Americans was looking for some pen, which could be used in space without troubles, They invested 1 000 000 $ in research and finally had one. Russians in the meantime used pencils. :-) (If you do not like Russians just switch the roles ;-) ) So we found Maven2 usefull with small to mid project with some commonly used libraries but here it stops. Once you set up good dependencies in Ant you well understand what library you use and why (maven shields you from this in some way) and yuo are able to solve troubles with build system fast. We do not really to care about looking for jars in google. Using Maven it is not that time saving. It is more confortable I agree, but not worth the time to solve Maven troubles. There is lot of buzz about \"Convention over configuration\", But if that convention is badly designed, like Maven project layout, our aproach is flexibility over convention. (Jsp is convention but then came grrat wicket wchich is typical flexibility over convention, or good convention over bad convention :-) ). But reality besides Rails and Wicket I did not see any good convention (over configuration). EnD of off topic: Uff ;-) Robert ----- Originálna Správa ----- Od: Jonathan Locke Komu: Poslaná: 06.09.2007 04:07 Predmet: Re: Wicket libraries > > > not only would the download be bigger, but there would be all kinds of > licensing headaches. some jar files might not even be legally distributed > in an aggregated download. i also hated maven at first, but you do get > used to it and it has gotten a LOT better (even if gosling is still a better > concept and foundation for a build system ;-)). > > > Al Maw wrote: > > > > Robo wrote: > >> Why there is no complete distribution of jar`s, needed to run Wicket > >> aplication just \\\"out of the box\\\". it is a little bit boring to find > >> out that I also need to download slf4j and velocity. I uderstand that > >> this info is writen on your page but I would expect just download one tar > >> (zip) unpackit to my classpath write demo and run it. > > > >> Contrary to lib where one would expect them they are included in > >> example`s war. > > > > We give you a ready-to-run WAR file which has all the dependencies for > > the projects. > > > > If we included the JAR files in addition to this, we\'d double the size > > of the download. It\'s an already-sizeable 14.8Mb for the ZIP. > > > > If you use Maven 2, it will manage the dependencies for you. If you > > choose to manage your dependencies manually, then you will obviously > > have some work to do. > > > >> and understand why I need org.apache.velocity packages when I do not use > >> it, is simply confusing me. does Wicket from clear and nice programming > >> go to something unclear and confused? > > > > >> And can someone point me to some link where there is explained why when I > >> develop simple HelloWorld application I need also org.apache.velocity. > > > > You don\'t. You need that for things that use the wicket-velocity > > project. Such as wicket-examples, which has example code for that. > > > > If you want a complete list of dependencies for each project, please > > find it here: > > > > http://herebebeasties.com/static/wicket-dependencies.txt > > > > > > Regards, > > > > Al > > -- > > Alastair Maw > > Wicket-biased blog at http://herebebeasties.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: > http://www.nabble.com/Wicket-libraries-tf4383758.html#a12514400 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > __________ http://www.inzeraty.sk/ - Bezplatná inzercia v najobľúbenejších kategóriách --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
