[
http://jira.codehaus.org/browse/MAVENUPLOAD-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=225394#action_225394
]
Blaine Simpson commented on MAVENUPLOAD-2788:
---------------------------------------------
By the way, I did use the deploy:deploy-file mojo to create the POMs that are
currently deployed and unusable. The mojo created them in the unusable state
without complaint.
> Remove artifacts
> ----------------
>
> Key: MAVENUPLOAD-2788
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2788
> Project: Maven Upload Requests
> Issue Type: Wish
> Reporter: Blaine Simpson
>
> Simple directory removal request.
> I do not want a Maven Upload, but just to wipe some artifacts that you are
> already mirroring to ibiblio (so that I can fix them). I am only opening
> this issue under this project because there is no other relevant "project" to
> fix issues with artifacts already in place. I figure that the techs who can
> work Upload tickets should know how to get to the mock-ftp staging or ibiblio
> production servers and know where the maven2 artifacts reside there.
> My problem is, you already picked up, by rsync, my new resources for my new
> project version 2.0.0. There was a mistake in the .pom files which was
> discovered after your pick-up. Not a big deal with the .pom mistake-- I
> fixed that in 5 minutes. But your rsync pickup job refuses to modify
> existing hosted artifacts, very likely because of the --ignore-existing
> switch that you use for rsync.
> If you could just get on the staging or production servers as needed and wipe
> out all of the 2.0.0 subdirectories at the level
> http://repo2.maven.org/maven2/org/hsqldb/*/2.0.0/ , that should be all that
> is needed (there are 4 directories at the same exact level, all grandchildren
> of http://repo2.maven.org/maven2/org/hsqldb/).
> I have a lot of experience with rsync, and with UNIX and scripting generally,
> so let me know if I can help in any way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
