You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Jason van Zyl (JIRA)" <ji...@apache.org> on 2009/02/09 05:42:59 UTC
[jira] Created: (INFRA-1896) Track projects that want to use the
Nexus repository infrastructure for releases
Track projects that want to use the Nexus repository infrastructure for releases
--------------------------------------------------------------------------------
Key: INFRA-1896
URL: https://issues.apache.org/jira/browse/INFRA-1896
Project: Infrastructure
Issue Type: Task
Security Level: public (Regular issues)
Reporter: Jason van Zyl
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-1896) Track projects that want to use the
Nexus repository infrastructure for snapshots/releases deployment
Posted by "Jason van Zyl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl 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.
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
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)
> Reporter: Jason van Zyl
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-1896) Track projects that want to use the
Nexus repository infrastructure for snapshots/releases deployment
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (INFRA-1896) Track projects that want to use the
Nexus repository infrastructure for snapshots/releases deployment
Posted by "Joe Schaefer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Schaefer updated INFRA-1896:
--------------------------------
Component/s: Nexus
> 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
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-1896) Track projects that want to use the
Nexus repository infrastructure for releases
Posted by "Jason van Zyl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl 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.
> Track projects that want to use the Nexus repository infrastructure for releases
> --------------------------------------------------------------------------------
>
> Key: INFRA-1896
> URL: https://issues.apache.org/jira/browse/INFRA-1896
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Reporter: Jason van Zyl
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-1896) Track projects that want to use the
Nexus repository infrastructure for snapshots/releases deployment
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
#asfinfra IRC Bot updated INFRA-1896:
-------------------------------------
Assignee: Brian Fox
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-1896) Track projects that want to use the
Nexus repository infrastructure for snapshots/releases deployment
Posted by "Jason van Zyl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl 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
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.
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.
> 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)
> Reporter: Jason van Zyl
>
> 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
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-1896) Track projects that want to use the
Nexus repository infrastructure for snapshots/releases deployment
Posted by "Jason van Zyl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl updated INFRA-1896:
---------------------------------
Summary: Track projects that want to use the Nexus repository infrastructure for snapshots/releases deployment (was: Track projects that want to use the Nexus repository infrastructure for releases)
> 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)
> Reporter: Jason van Zyl
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-1896) Track projects that want to use the
Nexus repository infrastructure for snapshots/releases deployment
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed INFRA-1896.
----------------------------
Resolution: Fixed
Now that the guide is ready, we no longer need this task open to serve as docs:
http://www.apache.org/dev/publishing-maven-artifacts.html
> 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.
[jira] Updated: (INFRA-1896) Track projects that want to use the
Nexus repository infrastructure for snapshots/releases deployment
Posted by "Jason van Zyl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl 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
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.
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
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.
> 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)
> Reporter: Jason van Zyl
>
> 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
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.