On Jan 4, 2008 12:31 PM, simon <[EMAIL PROTECTED]> wrote: > Matt has pointed out on the user list that the official maven repo has > some artifacts from core-1.2.1, dated 22 dec. > > http://repo1.maven.org/maven2/org/apache/myfaces/core/myfaces-core-project/ > http://repo1.maven.org/maven2/org/apache/myfaces/core/myfaces-impl/ > > There are core-project and myfaces-impl from 1.2.1, but no myfaces-api. > > I guess these were accidentally published, and that they should be > removed from the mirrors ASAP. Anyone know how this can be done?
I'd delete them from the m2-ibiblio-rsync-repository, and then write to [EMAIL PROTECTED] stating that they were not officially released and requesting that they be removed from central. Carlos or Jason will probably have to get involved. Any idea how it happened? > I also see that there is a tag for 1.2.1 in svn: > http://svn.apache.org/repos/asf/myfaces/core/tags/1_2_1/ > > This seems like a bad idea as there is no 1.2.1 release in existence. If > a tag is needed for the release-candidate, then the dir name should have > "RC" in it, and be renamed to the final 1_2_1 name after publication of > the release candidate as an actual release. Does the > maven-release-plugin allow this? It's not a problem for there to be a tag and staged artifacts that never passed a vote. They just shouldn't be available for download as an official release. -- Wendy
