jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jukka Zitting <jukka.zitt...@gmail.com>
Subject Re: Using a repository manager (Was: [jira] Created: (JCRSITE-11) Prevent accidental release deployments)
Date Mon, 23 Feb 2009 16:33:02 GMT

On Wed, Feb 11, 2009 at 5:46 PM, Jukka Zitting <jukka.zitting@gmail.com> wrote:
> On Mon, Feb 9, 2009 at 1:28 PM, Jukka Zitting (JIRA) <jira@apache.org> wrote:
>> The Maven people are currently setting up a new repository.apache.org repository
>> manager that nicely supports staged deployment. [...]
> I have now requested access to this repository manager (see INFRA-1899
> [1]). I'm planning to try how well it works for deploying snapshots
> from our Hudson builds and for staging and publishing official
> releases.
> If it works fine, then I would propose that we use
> repository.apache.org to replace the current m2-snapshot-repository as
> the location of our snapshots [...]

I have now updated our main Hudson builds to deploy Jackrabbit
snapshots to https://repository.apache.org/content/repositories/snapshots/
instead of http://people.apache.org/repo/m2-snapshot-repository/.
Please update any downstream references.

The main benefits of the new repository manager are simpler Hudson
configuration (I no longer need a cronjob on p.a.o to sync snapshots)
and automatic cleanup of old snapshots even when using unique snapshot
versions. Yes, the Jackrabbit snapshot now once again come with unique
version numbers instead of just the fixed -SNAPSHOT.

Let me know if you face nay problems with the new snapshot repository.
If everything goes fine, I will remove the org/apache/jackrabbit tree
from m2-snapshot-repository in about a week from now.


Jukka Zitting

View raw message