There's a bug logged on JIRA about 'uniqueVersion' property. I think its
fixed for release 2.0.5 (not out yet).
So until 2.0.5 is out its a manual process, I guess :-)
cheers,
Rahul
----- Original Message -----
From: "Steven E. Harris" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, January 09, 2007 5:56 AM
Subject: Deploying to snapshot repository: controlling accretion
I'm experimenting with deploying snapshots to an internal snapshot
repository, using the scpexe URL scheme for now. I noticed that each
time I deploy, maven generates a fresh version¹ and places a new set
of files in the repository.
Is there any automated way to clean up old snapshots, or control how
many of these versioned sets of files are left sitting in the
repository? I haven't actually used the deploy goal much, but I
anticipate that we'd never want more than three snapshot versions
sitting around in the repository. Is it my responsibility to purge the
old versions manually?
Footnotes:
¹ The uniqueVersion parameter is left to its default, true.
--
Steven E. Harris
---------------------------------------------------------------------
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]
