I have a scenario where I need to use maven-release-plugin to cut the daily build. After a while I need to purge some and leave some latest ones.
A tool to remove unneeded artifacts and metadata files is great. I think Brett mentioned that maven repo manager can do that ( not release yet) -D On 3/24/06, Nic Holbrook <[EMAIL PROTECTED]> wrote: > > If they are the same version as the production one is going to be, why > not just overwrite them with the official production version? You lose > your test code, but thats seems to be a compromise for not wanting to > tag another way. > > Nic > > Wendy Smoak wrote: > > >After you have deployed an artifact, is there a way to 'un-deploy' it? > > We have "test builds" deployed to a repository, (they are more or > >less release candidates, with the bonus of not having to re-tag and > >create new artifacts if they are judged to be of sufficient quality to > >be released.) > > > >If a test build doesn't make the grade, I need to remove it from the > >repository. It was easy enough to just delete the directories > >containing the artifacts, but that version number is still listed in > >the metadata. Is that going to cause a problem? > > > >Thanks, > >Wendy > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > >[tch] > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
