[
http://jira.codehaus.org/browse/MAVENUPLOAD-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97633
]
Christian Schulte commented on MAVENUPLOAD-1483:
------------------------------------------------
As it seems, I have made a huge mistake. There is a repository containing
release artifacts at
<http://repository.jdtaus.org/releases>
I asked a while ago to sync this repository with ibiblio via rsync which was
commited to your subversion repository. Everything worked as needed. When
deploying the final 1.0 release artifacts to this repository I made a mistake
(I removed all deprecations from the code introduced during beta-testing, since
I did not want to release final 1.0 artifacts containing deprecations) which
lead to all old artifacts getting broken because I defined all dependencies by
using <version>RELEASE</version>. So I took a look on how rsyncing is done with
the repository and thought removing artifacts from the repository will also be
handled by rsync. I then moved the whole repository to
<http://repository.jdtaus.org/deprecated>
and just deployed the final 1.0 release artifacts to the new releases
repository which was now an empty directory on my machine. What happens now is
that I can see rsync syncing the releases repository as it did before, but the
changes are not promoted to ibiblio anymore. The recent releases repository
just contains 1.0 artifacts without all the broken 1.0-beta-x versions.
So what actually happens is that e.g.:
<http://www.ibiblio.org/maven2/org/jdtaus/common>
does not match
<http://repository.jdtaus.org/releases/org/jdtaus/common>.
anymore although rsync seems to work correctly.
The question is what to do I on my side. Leave the "new" releases repository as
is (without the broken artifacts) and hope that ibiblio will catch up somewhen
(hopefully removing all the broken beta artifacts), or should I move the
deprecated repository back into place so that syncing to ibiblio starts working
again ?
Currently the artifacts I deploy to the "new" releases repository do not show
up on ibiblio anymore. It would be really great if it would be possible to
remove the broken beta artifacts (use the new releases repository as is) but I
could also move the old (deprecated) directory back in place.
What I mean is, I could log into the machine serving the repository via rsync
and do a
$ rm -rf releases
& mv deprecated releases
and ibiblio should be in sync with the repository again (but would contain lots
of broken artifacts).
I am somehow stuck and don't know what to do, to get the sync working again.
If removing artifacts is not desired, that would be no problem since I have the
backup available. If the broken artifacts can be removed, the current releases
repository contains all working final 1.0 artifacts so that it would be
sufficient, if ibiblio would match that directory.
I am no native english speaking person so I am having a hard time trying to
explain the problem...sorry!
> Please synchronize the jDTAUS repository
> ----------------------------------------
>
> Key: MAVENUPLOAD-1483
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1483
> Project: maven-upload-requests
> Issue Type: Task
> Reporter: Christian Schulte
> Assignee: Carlos Sanchez
> Attachments: org.jdtaus.sh
>
>
--
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
