[CONTINUUM-1633] release using mvn release plugin

• Type: Improvement
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.1
• Component/s: Release
• Labels: backlog-to-cleanup
• Flags: Patch
• Assignee: Unassigned
• Reporter: Benoit Decherf
• Created: 24/Jan/08 03:27
• Updated: 05/Apr/15 14:44

Description

I think that the release process should use the release plugin rather than the maven-release classes directly.

Actually, it's possible to choose the maven installation to execute the compilation in continuum, BUT the maven version used to release a project can't be changed because of the compilation/runtime dependency of continuum-release.

Also, if I configure the release plugin in pom.xml (for default values or to use a specific version of the plugin), this is ignored by continuum.

What do you think about externalize the release execution using external command line as you do to execute scheduled goals ? Is there any blocker issue so that it's not possible ?

Issue Links

• is related to: CONTINUUM-2364 Partial release plugin configuration loses the defaults for unconfigured items
• relates to: CONTINUUM-1572 Release should support Build Environments (formerly called Continuum Profiles)
• relates to: CONTINUUM-2028 Continuum release prepare should use maven-release-plugin scmCommentPrefix configuration in pom