Maven 2.x Release Plugin

add an option to set the profile(s) used to perform the release

Details

  • Type: Wish Wish
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 2.0-beta-7
  • Fix Version/s: 2.0-beta-8
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

release:perform runs maven to build the released artifact with the current active profiles (AFAIK)
It would be nice to have a configuration parameter to set release profiles, so that it does not depend on user environment.

Issue Links

This issue relates to:
MRELEASE-410 Allow specifying specific profiles to execute in the prepare mojo Major Open

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
nicolas de loof added a comment -

new "releaseProfiles" mojo parameter for coma separated list of profiles to enabled, in addition to the ones allready actives on maven instance running release:perform goal.

Show
nicolas de loof added a comment - new "releaseProfiles" mojo parameter for coma separated list of profiles to enabled, in addition to the ones allready actives on maven instance running release:perform goal.
Hide
Permalink
Basil James Whitehouse III added a comment -

Can this profile also be activated when running release:prepare?

I have a multi-module project that builds a distribution archive that is only activated by a profile since developers don't normally need it and it's quite large (80 MB) and don't want to occupy space in the local Maven repo. In order for this distribute module to have it's version number changed by the release plugin it needs to be part of the release:prepare .

For now I use the performRelease property to activate it, but I'd rather not use that since it could also activate other things I don't normally need. E.g. mvn --batch-mode release:prepare release:perform -DperformRelease

Show
Basil James Whitehouse III added a comment - Can this profile also be activated when running release:prepare? I have a multi-module project that builds a distribution archive that is only activated by a profile since developers don't normally need it and it's quite large (80 MB) and don't want to occupy space in the local Maven repo. In order for this distribute module to have it's version number changed by the release plugin it needs to be part of the release:prepare . For now I use the performRelease property to activate it, but I'd rather not use that since it could also activate other things I don't normally need. E.g. mvn --batch-mode release:prepare release:perform -DperformRelease

People

Vote (1)
Watch (3)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.