If you're just getting started with Maven / Wicket QuickStart, etc, I'd suggest the following...
Go to this page and follow the instructions on it: http://wicket.apache.org/quickstart.html Basically, after you have Maven properly installed, you go to the page above, and generate the Maven command to create your project folder, like: mvn archetype:create -DarchetypeGroupId=org.apache.wicket -DarchetypeArtifactId=wicket-archetype-quickstart -DarchetypeVersion=1.3.3 -DgroupId=com.mycompany -DartifactId=myproject After you've run that, you will have a folder that has your complete setup for a Wicket application. Then, go into Eclipse, create a new java project from existing source, and point it to the folder you just created. Then, you can use these commands to get you along: This one will setup your classpath in Eclipse and attach the source for everything that it can find source for: mvn eclipse:eclipse -DdownloadSource=true Create your WAR: mvn clean package Run your test cases: mvn test Create the WAR and put it into your local (or a distributed - with some configuration) repository: mvn install To run your application, I find the easiest way is after importing the project into Eclipse, and running mvn eclipse:eclipse, just run the Start.java as a java application from within Eclipse. This will allow you to run in debug, attach to the debugger, etc.... Hope this helps, Jeremy Thomerson http://www.wickettraining.com On Wed, May 7, 2008 at 3:01 PM, Frank Silbermann <[EMAIL PROTECTED]> wrote: > Warren provided a link > (http://herebebeasties.com/2007-10-07/wicket-quickstart/) to a very > helpful site that demonstrates: > > 1. Using Maven2 to download the Wicket Quickstart project, > 2. Downloading the Eclipse plug-in for Maven2, > 3. Configuring Eclipse to find Maven2, and > 4. Running the Quickstart application in Eclipse. > > I'm a bit confused as to the relationship between these three. The > Maven2 documentation says that this plug-in allows maven to be run from > within Eclipse, rather than using the command-line. But in the demo it > seems to be doing more than that. In the demo, Eclipse complains about > unknown dependencies in the Quickstart project until a a configuration > variable in Eclipse is set to a Maven2 directory; then Eclipse finds the > Quickstart's dependencies. What exactly is the relationship between > Maven2 and Eclipse when using this plug-in? Does it tell Eclipse to > forgo its normal project description format and instead rely on Maven2 > to describe the project and replace Eclipse' native build commands? > > When the demonstrator downloads the Eclipse plug-in for Maven2 (or is it > rather a Maven2 plug-in for Eclipse?), Maven downloads a bunch of stuff > including a Wicket jar. That surprised me. Why would it assume that a > user of Maven2 with Eclipse would need Wicket? Is Maven2 actually smart > enough to look in the Quickstart project to see what Eclipse needs to > run it? What if I had installed Maven2 and the Eclipse plug-in _before_ > downloading the Quickstart project to begin developing in Wicket? > > Please for give my naivite, but Eclipse, Maven2 and the Wicket > Quickstart project are all new to me, and I'm getting as to what exactly > is the flow of information between these components as we set up the > environment. > > /Frank > > > -----Original Message----- > From: Warren [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 01, 2008 3:58 PM > To: users@wicket.apache.org > Subject: RE: Difficulty getting QuickStart > > I was having some problems until I went to this site: > > http://herebebeasties.com/2007-10-07/wicket-quickstart/ > > There is a screencast there that will show you everything. It was real > helpful. > > > -----Original Message----- > > From: Frank Silbermann [mailto:[EMAIL PROTECTED] > > Sent: Thursday, May 01, 2008 1:52 PM > > To: users@wicket.apache.org > > Subject: Difficulty getting QuickStart > > > > > > I wrote in earlier about a problem I had in less-old releases of > > Wicket 1.2. Since no more work is being done on that version, I > > thought I'd try the sample on Wicket 1.2. I figured the easiest > > approach was to download the Wicket 1.3 QuickStart application. That > > requires Maven, which I've never before used. I downloaded and > > installed Maven (I assume correctly) and then followed the > > instructions to get the QuckStart application, but the Maven command > > failed with the following output. Can anyone tell me what I did > > wrong? (I apologize if this is really a Maven question, but obtaining > > QuickStart is my only reason for messing with Maven.) > > > > C:\>mvn archetype:create -DarchetypeGroupId=org.apache.wicket > > -DarchetypeArtifactId=wicket-archetype-quickstart > > -DarchetypeVersion=1.3.3 -DgroupId=com.mycompany > > -DartifactId=myproject [INFO] Scanning for projects... > > [INFO] Searching repository for plugin with prefix: 'archetype'. > > [INFO] org.apache.maven.plugins: checking for updates from central > > [WARNING] repository metadata for: 'org.apache.maven.plugins' could > > not be retrieved from repository: central due to an error: Error > > transferring file [INFO] Repository 'central' will be blacklisted > > [INFO] > > ---------------------------------------------------------------------- > > -- > > [ERROR] BUILD ERROR > > [INFO] > > ---------------------------------------------------------------------- > > -- [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' > > does not exist or no valid version could be found [INFO] > > ---------------------------------------------------------------------- > > -- [INFO] For more information, run Maven with the -e switch [INFO] > > ---------------------------------------------------------------------- > > -- > > [INFO] Total time: 21 seconds > > [INFO] Finished at: Thu May 01 15:42:12 CDT 2008 [INFO] Final Memory: > > 1M/2M [INFO] > > ---------------------------------------------------------------------- > > -- > > > > > > > > /Frank > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > >
