maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (MRELEASE-665) Describe how to release a patched external project
Date Tue, 08 Mar 2011 12:29:22 GMT
Describe how to release a patched external project
--------------------------------------------------

                 Key: MRELEASE-665
                 URL: http://jira.codehaus.org/browse/MRELEASE-665
             Project: Maven 2.x Release Plugin
          Issue Type: Task
          Components: documentation
            Reporter: Robert Scholte
            Priority: Minor


When releasing, all dependencies should be of a final version.
If it depends on patched versions of certain projects, you'd have to release those patched
versions first to your own repo-manager (if you can't wait for the real release).

For deploying SNAPSHOT's it would be
{{mvn deploy -DaltDeploymentRepository=id::layout::url}}

For releasing I think it should be something like:
{{mvn release:prepare -DtagBase=}}
{{mvn release:perform -Darguments="-DaltDeploymentRepository=id::layout::url" -Dgoals=deploy}}
Also, the version should be based on the latest release version, extended with something like
{{-1-myCompany}}

I believe this is realistic usecase and it would be great if it could be documented.

-- 
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

        

Mime
View raw message