This is indeed a buggy feature: the retrieved snpashot dependency, in the case of a war module for example, is sometime included as mydependency-1.0-SNAPSHOT.jar, and sometimes as mydependency-1.0-TIMESTAMP.jar. If a mvn clean is not done, a dependency can also be included twice as mydependency-1.0-TIMESTAMP1.jar and mydependency-1.0-TIMESTAMP2.jar.
My two cents, Sebastien -----Original Message----- From: amit kumar [mailto:[EMAIL PROTECTED] Sent: Monday, February 18, 2008 09:52 To: Maven Users List Subject: Re: SNAPSHOT It seems to work for me. Whenever a new SNAPSHOT version(1.0.0-SNAPSHOT) is deployed to the reposiroty maven stores it with timestamp witn in the 1.0.0-SNAPSHOT folder. As I can see the artifact-1.0.0-SNAPSHOT.jar keeps on getting updated corresponding to the latest deployed jar. So in the repository the 1.0.0-SNAPSHOT folder has all the so far deployed jar files along with the timestamp and a artifact-1.0.0-SNAPSHOT.jar, which gets retrieved. Regards, Amit On 2/18/08, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > On Feb 17, 2008 10:14 PM, Ryan H. <[EMAIL PROTECTED]> wrote: > > > If my maven2 repository persists each artifact with time stamp as > > part of their filename, is SNAPSHOT version still going to work? > > Yes. It uses the metadata file in the repository to decide which > timestamped file to retrieve. > > (Are you using just 'SNAPSHOT' as a version? Usually it's > 1.0-SNAPSHOT or similar.) > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
