This is because the dependency plugin looks for the existing file before copying over. We originally had the ability to force an overwrite but took it out before release. The reasoning was that artifacts should be non-mutatable in the repo. Ie if we get v1 copied, we shouldn't copy v1 again. This probably doesn't fly well for snapshots though. We could possibly look for snapshots and always overwrite them, or maybe try something else. Anyone have suggestions? There are several new features in the svn version 1.1, I could get this added before the next release.
The work around is to do a clean first. -----Original Message----- From: Christopher Cobb [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 10, 2006 10:31 AM To: 'Maven Users List' Subject: [m2 dependency plugin] updated dependency not copied P1 depends on P2 which depends upon P3. P1 uses the dependency plug in and P2.jar and P3.jar are successfully copied into P1's target tree. Now P3 changes and a new file (different size, different timestamp) is installed in the local repository. When P1 is built, the new version of P3.jar is not copied over the existing version. I briefly saw some similar traffic about the dependency plug in but I'm not sure if covered exactly this case so I thought I would mention it. ----------------------------------------- Attention: Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you received this in error, please contact the sender and delete the material from any system and destroy any copies. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
