[
http://jira.codehaus.org/browse/MAVENUPLOAD-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=225393#action_225393
]
Blaine Simpson commented on MAVENUPLOAD-2788:
---------------------------------------------
I understand very well the confusion that can be caused by changing labeled
artifacts, but there are cases like this where those risks to not apply, and as
this project's build and packaging lead, I am in the best position to
distinguish.
"How serious is the error in the POM? Does it validate?" It is serious and
nobody in the world has successfully pulled down via Maven or Ivy using those
POMs. Right now, we have a large number of users forced to customize their
resolvers because I can't update my own POMs on ibiblio.
This is a major release, 2.0.0, which thousands of users have waited for for
years, and though I wear several hats, a consensus is required before we roll
new releases. This is a full-blown database, bundled by many third party
products, including OpenOffice. We don't roll releases without much
consultation and preparation.
I certainly do admit that the POM mistake is my fault. I purposefully did not
spend time trying to validate the POMs before uploading because I intended to
do thorough end-to-end testing after it was uploaded but before announcing
Maven availability. (One can't test like an end user until after the artifacts
are at Ibiblio). It was quite a shock to me to find that you give Project
authors ultimate privileges to author their POMs, corrupt their artifacts,
allow them to upload without any validation, but then become cautious and don't
allow them to fix mistakes to their own work.
Please advise if you or somebody else there can allow me to update my own POMs.
> 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
