[
https://issues.apache.org/jira/browse/MRELEASE-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-665.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Describe how to release a patched external project
> --------------------------------------------------
>
> Key: MRELEASE-665
> URL: https://issues.apache.org/jira/browse/MRELEASE-665
> Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)
