jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
Signup
Maven Project Web Site
  • Maven Project Web Site
  • MNGSITE-79

Release instructions unclear

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Labels:
    None
  • Number of attachments :
    0

Description

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.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Brett Porter added a comment - 18/Mar/09 2:33 PM

2/3/4 apply to the docs here, but really an INFRA ticket should be opened to get generic stuff made available.

Show
Brett Porter added a comment - 18/Mar/09 2:33 PM 2/3/4 apply to the docs here, but really an INFRA ticket should be opened to get generic stuff made available.
Hide
Permalink
Francis De Brabandere added a comment - 24/Jun/09 2:48 PM

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

Show
Francis De Brabandere added a comment - 24/Jun/09 2:48 PM 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
Hide
Permalink
Dennis Lundberg added a comment - 03/Nov/11 2:09 PM

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/

Show
Dennis Lundberg added a comment - 03/Nov/11 2:09 PM 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/

People

  • Assignee:
    Dennis Lundberg
    Reporter:
    David Jencks
Vote (0)
Watch (0)

Dates

  • Created:
    18/Mar/09 1:31 PM
    Updated:
    03/Nov/11 2:09 PM
    Resolved:
    03/Nov/11 2:09 PM
  • Atlassian JIRA (v5.2.7#850-sha1:b2af0c8)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.