> -----Original Message----- > From: James CE Johnson [mailto:[EMAIL PROTECTED]] > Sent: 20 August 2002 01:12 > To: Turbine Maven Users List > Subject: Two b4 -> b5 migration issues > > Hey all... > > First, it looks like ~/build.properties doesn't override > project.properties any more even though I have > > <!-- Allow any user specific values to override the defaults --> > <property file="${user.home}/build.properties" /> > <!-- Allow user defaults for this project --> > <property file="build.properties" /> > <!-- Set default values for the build --> > <property file="default.properties" /> > > in my maven.xml file. > > > Second, what happened to maven.dependency.set? We have a post-compile > action (converting it to a goal thingy now) that sets up an exploded > warfile in /tmp/webapps/myapp.war for jetty to play with. We need to > copy the list of jars on which the app is dependent and were using > maven.dependency.set for that. Is there a better way now? >
Yes, there is. The war plugin has a "war:webapp" goal (you can get a list of goal by typing "maven -g" on the command line) that prepares an exploded war (including libs). Then you simply need to copy that directory to wherever you want it to go. Or you can simply use the "war:build-war" goal and use the ant <unwar> task to unwar it directly to your location. -Vincent > Thanks, > J > > > > -- > To unsubscribe, e-mail: <mailto:turbine-maven-user- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:turbine-maven-user- > [EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
