You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "David Jencks (JIRA)" <ji...@codehaus.org> on 2009/03/18 19:32:13 UTC
[jira] Created: (MNG-4095) Release instructions unclear
Release instructions unclear
----------------------------
Key: MNG-4095
URL: http://jira.codehaus.org/browse/MNG-4095
Project: Maven 2
Issue Type: Improvement
Components: Documentation: General
Reporter: David Jencks
Refers to http://maven.apache.org/developers/release/releasing.html
This is AFAICT the de-facto advice on best practices for apache projects that want to use maven... if there's more information elsewhere it should be linked from here. As such it is sorely lacking some basic info such as...
1. It applies to projects using the apache pom version 5 which implies you are deploying to nexus. This needs to be stated up front and the consequences outlined (e.g. getting someone (who?) to move old stuff onto nexus, and what happens to a large collection of projects (e.g. portals or geronimo) that may not want to move everything at once)
2. if <altDeploymentRepository>${deploy.altRepository}</altDeploymentRepository> in the release profile is actually recommended please document where the value actually comes from.
3. In the "Release Process for part of Maven" 1.b it says "Verify that all pom.xml files have an SCM definition." I think this is wrong. IIUC only root poms in a multimodule project should define scm.
4. In the note on the settings.xml server definition of apache.snapshots.https please document that it is used from the apache 5 pom. Also, I think that the password required is your apache svn password rather than a possible p.a.o password. There is at least one other reference to logging on to nexus with "apache credentials" that should be more specifically "apache svn username and password"
5. If this is the de-facto advice to apache projects wishing to move from the file based repo to apache's nexus it needs to be findable through google. Linking it to INFRA-1885 would be good. Linking from the front page of the maven docs would be good. More generic separate docs would be better.
--
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
[jira] Commented: (MNGSITE-79) Release instructions unclear
Posted by "francisdb (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGSITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181413#action_181413 ]
francisdb commented on MNGSITE-79:
----------------------------------
6. the settings.xml example should have as profile id "apache-release" instead of "release"
and you might want to point the user to version 6 of the apachepom
> Release instructions unclear
> ----------------------------
>
> Key: MNGSITE-79
> URL: http://jira.codehaus.org/browse/MNGSITE-79
> Project: Maven 2 Project Web Site
> Issue Type: Improvement
> Reporter: David Jencks
>
> Refers to http://maven.apache.org/developers/release/releasing.html
> This is AFAICT the de-facto advice on best practices for apache projects that want to use maven... if there's more information elsewhere it should be linked from here. As such it is sorely lacking some basic info such as...
> 1. It applies to projects using the apache pom version 5 which implies you are deploying to nexus. This needs to be stated up front and the consequences outlined (e.g. getting someone (who?) to move old stuff onto nexus, and what happens to a large collection of projects (e.g. portals or geronimo) that may not want to move everything at once)
> 2. if <altDeploymentRepository>${deploy.altRepository}</altDeploymentRepository> in the release profile is actually recommended please document where the value actually comes from.
> 3. In the "Release Process for part of Maven" 1.b it says "Verify that all pom.xml files have an SCM definition." I think this is wrong. IIUC only root poms in a multimodule project should define scm.
> 4. In the note on the settings.xml server definition of apache.snapshots.https please document that it is used from the apache 5 pom. Also, I think that the password required is your apache svn password rather than a possible p.a.o password. There is at least one other reference to logging on to nexus with "apache credentials" that should be more specifically "apache svn username and password"
> 5. If this is the de-facto advice to apache projects wishing to move from the file based repo to apache's nexus it needs to be findable through google. Linking it to INFRA-1885 would be good. Linking from the front page of the maven docs would be good. More generic separate docs would be better.
--
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
[jira] Moved: (MNGSITE-79) Release instructions unclear
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGSITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MNG-4095 to MNGSITE-79:
------------------------------------------
Component/s: (was: Documentation: General)
Complexity: (was: Intermediate)
Key: MNGSITE-79 (was: MNG-4095)
Project: Maven 2 Project Web Site (was: Maven 2)
> Release instructions unclear
> ----------------------------
>
> Key: MNGSITE-79
> URL: http://jira.codehaus.org/browse/MNGSITE-79
> Project: Maven 2 Project Web Site
> Issue Type: Improvement
> Reporter: David Jencks
>
> Refers to http://maven.apache.org/developers/release/releasing.html
> This is AFAICT the de-facto advice on best practices for apache projects that want to use maven... if there's more information elsewhere it should be linked from here. As such it is sorely lacking some basic info such as...
> 1. It applies to projects using the apache pom version 5 which implies you are deploying to nexus. This needs to be stated up front and the consequences outlined (e.g. getting someone (who?) to move old stuff onto nexus, and what happens to a large collection of projects (e.g. portals or geronimo) that may not want to move everything at once)
> 2. if <altDeploymentRepository>${deploy.altRepository}</altDeploymentRepository> in the release profile is actually recommended please document where the value actually comes from.
> 3. In the "Release Process for part of Maven" 1.b it says "Verify that all pom.xml files have an SCM definition." I think this is wrong. IIUC only root poms in a multimodule project should define scm.
> 4. In the note on the settings.xml server definition of apache.snapshots.https please document that it is used from the apache 5 pom. Also, I think that the password required is your apache svn password rather than a possible p.a.o password. There is at least one other reference to logging on to nexus with "apache credentials" that should be more specifically "apache svn username and password"
> 5. If this is the de-facto advice to apache projects wishing to move from the file based repo to apache's nexus it needs to be findable through google. Linking it to INFRA-1885 would be good. Linking from the front page of the maven docs would be good. More generic separate docs would be better.
--
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
[jira] Closed: (MNGSITE-79) Release instructions unclear
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNGSITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed MNGSITE-79.
----------------------------------
Resolution: Won't Fix
Assignee: Dennis Lundberg
The focus of these pages have changed since this issue was created. They now focus on releasing parts of the Maven project.
General ASF release instructions can be found at
http://www.apache.org/dev/publishing-maven-artifacts.html#maven and the ASF POM has its own website at
http://maven.apache.org/pom/asf/
> Release instructions unclear
> ----------------------------
>
> Key: MNGSITE-79
> URL: https://jira.codehaus.org/browse/MNGSITE-79
> Project: Maven Project Web Site
> Issue Type: Improvement
> Reporter: David Jencks
> Assignee: Dennis Lundberg
>
> Refers to http://maven.apache.org/developers/release/releasing.html
> This is AFAICT the de-facto advice on best practices for apache projects that want to use maven... if there's more information elsewhere it should be linked from here. As such it is sorely lacking some basic info such as...
> 1. It applies to projects using the apache pom version 5 which implies you are deploying to nexus. This needs to be stated up front and the consequences outlined (e.g. getting someone (who?) to move old stuff onto nexus, and what happens to a large collection of projects (e.g. portals or geronimo) that may not want to move everything at once)
> 2. if <altDeploymentRepository>${deploy.altRepository}</altDeploymentRepository> in the release profile is actually recommended please document where the value actually comes from.
> 3. In the "Release Process for part of Maven" 1.b it says "Verify that all pom.xml files have an SCM definition." I think this is wrong. IIUC only root poms in a multimodule project should define scm.
> 4. In the note on the settings.xml server definition of apache.snapshots.https please document that it is used from the apache 5 pom. Also, I think that the password required is your apache svn password rather than a possible p.a.o password. There is at least one other reference to logging on to nexus with "apache credentials" that should be more specifically "apache svn username and password"
> 5. If this is the de-facto advice to apache projects wishing to move from the file based repo to apache's nexus it needs to be findable through google. Linking it to INFRA-1885 would be good. Linking from the front page of the maven docs would be good. More generic separate docs would be better.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNGSITE-79) Release instructions unclear
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGSITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170186#action_170186 ]
Brett Porter commented on MNGSITE-79:
-------------------------------------
2/3/4 apply to the docs here, but really an INFRA ticket should be opened to get generic stuff made available.
> Release instructions unclear
> ----------------------------
>
> Key: MNGSITE-79
> URL: http://jira.codehaus.org/browse/MNGSITE-79
> Project: Maven 2 Project Web Site
> Issue Type: Improvement
> Reporter: David Jencks
>
> Refers to http://maven.apache.org/developers/release/releasing.html
> This is AFAICT the de-facto advice on best practices for apache projects that want to use maven... if there's more information elsewhere it should be linked from here. As such it is sorely lacking some basic info such as...
> 1. It applies to projects using the apache pom version 5 which implies you are deploying to nexus. This needs to be stated up front and the consequences outlined (e.g. getting someone (who?) to move old stuff onto nexus, and what happens to a large collection of projects (e.g. portals or geronimo) that may not want to move everything at once)
> 2. if <altDeploymentRepository>${deploy.altRepository}</altDeploymentRepository> in the release profile is actually recommended please document where the value actually comes from.
> 3. In the "Release Process for part of Maven" 1.b it says "Verify that all pom.xml files have an SCM definition." I think this is wrong. IIUC only root poms in a multimodule project should define scm.
> 4. In the note on the settings.xml server definition of apache.snapshots.https please document that it is used from the apache 5 pom. Also, I think that the password required is your apache svn password rather than a possible p.a.o password. There is at least one other reference to logging on to nexus with "apache credentials" that should be more specifically "apache svn username and password"
> 5. If this is the de-facto advice to apache projects wishing to move from the file based repo to apache's nexus it needs to be findable through google. Linking it to INFRA-1885 would be good. Linking from the front page of the maven docs would be good. More generic separate docs would be better.
--
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