For Web applications, you should specify dependencies with <properties><war.bundle>true</war.bundle></properties>, and they will automatically be copied into WEB-INF/lib by maven when you run war:webapp or war:war.
You can then point your server at target/webapp-name or target/webapp-name.war depending on which of the above goals you used. Have a look at the wiki for more best practices doing web application development. - Brett > -----Original Message----- > From: Christian Andersson [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 15 October 2003 10:33 PM > To: Maven Users List > Subject: best practise > > > Hi there,I just have some questions about "best practise" with maven.. > > before I used maven, I was using jbuilder (on windows), and > when running > the applications/websites/webapps I had created I used to run them > against the different build-directories directly. > > now that I use maven, I have changed that somewhat (I'm now > also using > linux) instead of running things against the build directory, I have > started to run things against the created jar files in the > maven local > repository. (I usually run maven with jar:install, and not just > java:compile) I then either have my script files pointing the > classpath > to those files, or I create softlinks (using ln -s) > > for example, in WEB-INF/lib I have soft-links to all the needed jar > files,which themselves are in the maven local repository. > > this works for me (at the moment), but i was wondering how > you are doing > things... are there other ways that are easier? better?more > futureproof? > > /Christian Andersson > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
