On 9/9/07, chickabee <[EMAIL PROTECTED]> wrote: > > > > 1. It is based on Maven. (I am not apache community with 25 projects > running > in parallel, I just want to make a small app using wicket. Maven is > overkill).
so write a quick ant script. the generated project itself has no dependencies on maven 2. It favors Jetty. ( Why even say Jetty, pom.xml has jetty dependencies > defined. ) notice they are scoped "test", so not required at deploy time. the great thing about jetty is this: you can quickly get your app running using mvn jetty:jetty command if you want. but even better, when developing you dont need to package your app into a war and deploy it - which are big time wasting steps when you have to do them every ten minutes. instead simply launch the included Start class and your app is up and running in seconds and includes hotswap. 3. It depends on log4j. (Newer JDK have all the logging features needed. ) we prefer log4j because it is more flexible then jdklogging, but this is a religious issue. all you have to do is remove the log4j jar and its slf4j equivalent and dropin the slf4j jdk log impl jar. 4. Advises the user to follow test driven development. (I want to be a bad > developer, is that okay?). huh? > All above default integrations and suggestions are unnecessary and > undermine > Wicket and make it less appealing to Non-Wicketers and possible adopters > of > this great phenomenon. you know, you are the first who seem to think that, ever. most new users find themselves at home with the project and dependencies quickstart generates. -igor This is not the responsibility of the Wicket > community to tell people what they should use or should not use. It is the > decision of wicket end user if they want to integrate wicket with a > double-cheese-burger :-) then let them do it on their own, but certainly > Quick Start rather be as rudimentary as possible, take it as a marketing > trick to entice the people to use wicket and make them fall in love with > wicket at first sight. > > Thank you all for listening. > > =============================================== > > > Craig Tataryn wrote: > > > > FYI Chickabee, if you are using Netbeans and use the Wicket plugin it is > > bundled with some helpful sample apps. > > > > Craig. > > > > On 9/8/07, chickabee <[EMAIL PROTECTED]> wrote: > >> > >> > >> Thanks for the great idea. > >> > >> It believe it will be good to put a few of the examples application in > >> their own folders and war files so that they can be studied > independently > >> without the clutter of 20 projects. > >> > >> Another thing I notice is that maven is the default build tool used > for > >> wicket, I guess it will be good to provide the ant build.xml, just in > >> case > >> someone does not want full maven features. > >> > >> --------------- > >> > >> > >> David Bernard-2 wrote: > >> > > >> > Welcome, > >> > > >> > If you want to start a blank project, try: > >> > > >> > $ mvn archetype:create -DarchetypeGroupId=org.apache.wicket > >> > -DarchetypeArtifactId=wicket-archetype-quickstart > >> > -DarchetypeVersion=1.3.0-beta3 > >> > -DgroupId=com.mycompany > >> > -DartifactId=myproject > >> > $ cd myproject > >> > $ more pom.xml > >> > > >> > then in this project try (copy/paste) the samples from the website. > >> > > >> > /david > >> > > >> > chickabee wrote: > >> >> Hi Wicketers, > >> >> > >> >> I tried wicket today and the example application was up and running > on > >> >> tomcat in no time, so that was the good part, after that if I like > to > >> >> create > >> >> a sample application on my own then I found no easy way to start. > >> >> > >> >> Examples are good to browse through and tell about wicket > >> capabilities, > >> >> however, not so good from learning point of view, All of the > examples > >> >> are > >> >> glued together in one big jar file and it is just not quick enough > to > >> >> create > >> >> a bare-bone application quickly and easily, > >> >> > >> >> I tried Quicket as mentioned in the readme file, however, Quickets > is > >> >> nothing but waste of time, because it is glued with Hibernate and > >> Spring > >> >> and > >> >> both should not be there to start with. > >> >> > >> >> Not a good experience trying wicket so far, I guess it's the time to > >> try > >> >> out > >> >> some more simpler app frameworks, > >> >> > >> >> -Thumbs Down to Wicket! > >> >> > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: [EMAIL PROTECTED] > >> > For additional commands, e-mail: [EMAIL PROTECTED] > >> > > >> > > >> > > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/First-Day-Disgust%21-tf4405663.html#a12569195 > >> Sent from the Wicket - User mailing list archive at Nabble.com. > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > > > -- > View this message in context: > http://www.nabble.com/First-Day-Disgust%21-tf4405663.html#a12576738 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
