hi, the problem is, that many to be users aren't that deep into oo programming as expected. also, people trying out wicket don't come from a maven background but maybe from plain jsp or other frameworks - or even php.
> $ 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 i've this suggestions now quite a few times and many users did actually say 'i don't have maven installed'. many users are just doing some web programming as hobby and trying out new things once in a while. it surely isn't the fault of the developers what knowledge people have when they stumble over wicket and find it worth a look. but to start with wicket for a newcomer it might be helpful to not be dependend on maven. on the other hand, i really don't understand why it's so hard to create a small wicket-project by hand: just set up a java project and add the wicket.jar to the build path and start coding. one has then to see for his own servlet container, but that one should know. regards, --- jan. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
