On Wednesday 12 November 2008 Troy Bull wrote: > I have a jar file that I maintain in my local maven repository (on my > workstation). It has had several versions, 2.0.2, 2.0.3 2.0.5 etc. > > I have a different project that is built with maven that uses this jar > file. If I change the jar file I update the version of the jar file. > > I then update my pom.xml file to fetch the new version of the jar. I > opened up my war file and noticed quite by accident that mvn is > including all the versions of the jar file in the WEB-INF/lib > directory. Is there something I need to do special to tell mvn to > only include the most recent version of the jar file?
Try a "mvn clean". This will solve your issue. The reason is, that the old JARs from previous builds remain in your target/<projectId>/ directory which is the directory that will be zipped to your final war file. hth, - martin
signature.asc
Description: This is a digitally signed message part.
