so far i have heard a bunch of bitching but very little in the way of concrete suggestions.
what are we to provide? a prebuilt project for eclipse? a prebuilt project for netbeans? a prebuilt project for idea? a prebuilt project for jedit? a prebuilt project for ant? a prebuilt project for make? a prebuilt project for buildr? a prebuilt project for foo? this is why we opted for maven, at least it can generate projects for all the major ides so we dont have to worry about it ourselves. the barrier to entry is incredibly low imho as it is - defined on our quickstart page of the website. 1) install maven2 - 5 minutes 2) run maven command to generate the project: 1 minute 3) run maven command to generate ide setup: 1 minute seven minutes and you have a project you can run inside your ide, or package into a war, or run from a command line with mvn jetty:run. -igor On 9/10/07, JulianS <[EMAIL PROTECTED]> wrote: > > > Behind chickabee's attempt to provoke the Wicket community (which Eelco > has > commendably resisted) lies a real message, namely that there are so many > web > frameworks out there, that people only have enough time to kick the tyres > before deciding which one to use, and therefore first impressions are > critical. > > This is one reason that ruby on rails has taken off--the combination of > Instant Rails and Active Record makes it the easiest framework to get a > fully database-enabled application up and running. > > Wicket has done a great job of making it easy to get up and running, but > there is always more to be done. > > Julian > > -- > View this message in context: > http://www.nabble.com/First-Day-Disgust%21-tf4405663.html#a12601343 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
