www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Fox (JIRA)" <j...@apache.org>
Subject [jira] Updated: (INFRA-1896) Track projects that want to use the Nexus repository infrastructure for snapshots/releases deployment
Date Tue, 28 Jul 2009 01:18:14 GMT

     [ https://issues.apache.org/jira/browse/INFRA-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brian Fox updated INFRA-1896:
-----------------------------

    Description: 
Several projects have expressed interest in using the Nexus managed repository for the staging/promotion
feature. I just want to keep track by making them sub-tasks of this main task.

Here is what the Maven Project is using if you want to understand what you would need to do
as a project:

http://maven.apache.org/developers/release/releasing.html

http://maven.apache.org/developers/committer-settings.html

There is also the staging documentation in the Nexus book:

http://www.sonatype.com/books/nexus-book/reference/staging.html

Also know that using Nexus requires us to take your artifacts off people.apache.org and place
them under the management of Nexus. But once this is done, staging and promoting is painless
and we will fully manage the repository (including snapshot management) and the sync artifacts
to central for you.

We would also ask that if you want to use Nexus for your project that you bring it up with
your projects and vote on the issue. When you decide if you could point us to the nabble thread
and record it in the accompanying JIRA issue that would be great.

When requesting access, please include the url of your project in svn, and if you know it,
the appropriate group from https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/asf-authorization
that should be imported to control your artifacts.


  was:
Several projects have expressed interest in using the Nexus managed repository for the staging/promotion
feature. I just want to keep track by making them sub-tasks of this main task.

Here is what the Maven Project is using if you want to understand what you would need to do
as a project:

http://maven.apache.org/developers/release/releasing.html

http://maven.apache.org/developers/committer-settings.html

There is also the staging documentation in the Nexus book:

http://www.sonatype.com/books/nexus-book/reference/staging.html

Also know that using Nexus requires us to take your artifacts off people.apache.org and place
them under the management of Nexus. But once this is done, staging and promoting is painless
and we will fully manage the repository (including snapshot management) and the sync artifacts
to central for you.

We would also ask that if you want to use Nexus for your project that you bring it up with
your projects and vote on the issue. When you decide if you could point us to the nabble thread
and record it in the accompanying JIRA issue that would be great.


> Track projects that want to use the Nexus repository infrastructure for snapshots/releases
deployment
> -----------------------------------------------------------------------------------------------------
>
>                 Key: INFRA-1896
>                 URL: https://issues.apache.org/jira/browse/INFRA-1896
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Nexus
>            Reporter: Jason van Zyl
>            Assignee: Brian Fox
>
> Several projects have expressed interest in using the Nexus managed repository for the
staging/promotion feature. I just want to keep track by making them sub-tasks of this main
task.
> Here is what the Maven Project is using if you want to understand what you would need
to do as a project:
> http://maven.apache.org/developers/release/releasing.html
> http://maven.apache.org/developers/committer-settings.html
> There is also the staging documentation in the Nexus book:
> http://www.sonatype.com/books/nexus-book/reference/staging.html
> Also know that using Nexus requires us to take your artifacts off people.apache.org and
place them under the management of Nexus. But once this is done, staging and promoting is
painless and we will fully manage the repository (including snapshot management) and the sync
artifacts to central for you.
> We would also ask that if you want to use Nexus for your project that you bring it up
with your projects and vote on the issue. When you decide if you could point us to the nabble
thread and record it in the accompanying JIRA issue that would be great.
> When requesting access, please include the url of your project in svn, and if you know
it, the appropriate group from https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/asf-authorization
that should be imported to control your artifacts.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message