Mike Kienenberger schrieb: > On 3/21/06, Daniel Bernstein <[EMAIL PROTECTED]> wrote: >> That's a good idea. I'll try it. By the way - I installed the svn eclipse >> plugin and maven 2.0. I'd like to try building the project and run it >> through the debugger (assuming I can't figure it about by the above method). >> What paths do I need to checkout and how can I build them with maven 2? ie >> - which directory/target do I need to run? > > On 3/22/06, Daniel Bernstein <[EMAIL PROTECTED]> wrote: >> Nevermind - I figured it out. I'll let you know what I find. Thanks for your >> help. > > Hopefully, you just followed the directions given at > > http://wiki.apache.org/myfaces/Building_With_Maven > > The only things I'd add to them is that I found it easiest to check > out the project with a non-Eclipse module (since you need to move the > checked-out directory outside of the Eclipse workspace). I used > TortoiseSVN for Windows. But you could also check it out using > Eclipse and manually move the files. > I agree with that checking out with subclipse has become contraproductive but subclipse works fine after the initial import.
> Once it's all up and going, I find using the JettyLauncher plugin and > Jetty to be the easiest way to run the examples or other JSF > applications from Eclipse. > Actually I think it is easiest to use the WTP or any other webtools plugin and setup the project structure the way in the properties that you can deploy automatically from the plugin into a running app server. (Works fine for me, I deploy the sandbox examples constantly that way)
