On Fri, 2004-07-16 at 12:20, Carlos Sanchez wrote:
> It's more a political question. AFAIK that repository shouldn't be sync to
> ibiblio, e.g. the Struts team has released version 1.2.1 but as long as it
> hasn't been voted as a public release they told me that it mustn't be
> uploaded to ibiblio, so they used repository at cvs.apache.org
Well that's perfectly fine, they are in complete control of what goes
into the directories we sync to ibiblio. At apache all committers have
access to the directory that goes to ibiblio. I started rejecting
requests to push Apache artifacts to Ibiblio a while ago, it's entirely
within the purview of a project at Apache to control what goes to the
central repository.
What I'm saying is that if a directory structure for snapshots were to
be made the same rules would apply. Apache probably doesn't want to
archive the snapshots forever and doesn't have the resources too but
Ibiblio does. All that needs to be done is a repository that houses the
snapshots and on a weekly basis it can be purged on the Apache side.
> What I meant was that we aren't currently deploying plugin snapshots and
> what I suggest is that we should deploy them to the repository at
> cvs.apache.org often (as it's very easy) and that way ibiblio repository is
> not messed up (the mail say that nothing must be deleted from ibiblio).
Rigth we just need a directory that's different from the one that is
used right now. I believe that one is for releases and infrastructure
wants that to mirrored and archived and doesn't want snapshots there. We
just need another directory that is of more of a transient nature where
snapshots can go to be sync'd with ibiblio and eventually wiped on the
Apache side.
> I will add
>
> # Repository to deploy to
> maven.repo.list=apachecvs
>
> # Repository to deploy snapshots
> maven.repo.apachecvs=scp://cvs.apache.org
> maven.repo.apachecvs.directory=/repository
> maven.repo.apachecvs.username=${maven.repo.apache.username}
> maven.repo.apachecvs.privatekey=${maven.repo.apache.privatekey}
> maven.repo.apachecvs.passphrase=${maven.repo.apache.passphrase}
>
> to plugin-parent project, so when making a release you only need to add
> -Dmaven.repo.list=apache.
You're going to have to differentiate though between releases and
snapshots if you actually want to deploy snapshots of anything.
You want to take care of this with infrastructure? Mark Diggory can also
point you in the right direction.
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org
happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...
-- Thoreau
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
