-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
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
So a simple overWrite flag per artifact would solve this for you?
-Original Message-
From: Christopher Cobb [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 11, 2006 8:41 AM
To: 'Maven Users List'
Subject: RE: [m2 dependency plugin] updated dependency not copied
-Original
That would work for me.
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 11, 2006 8:49 AM
To: Maven Users List
Subject: RE: [m2 dependency plugin] updated dependency not copied
So a simple overWrite flag per artifact would solve this for you
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
