Uploaded image for project: 'Maven Release Plugin'
  1. Maven Release Plugin
  2. MRELEASE-571

When collecting active profiles, the active profiles from parent poms are not considered

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.0
    • 2.4
    • perform, prepare
    • None
    • Patch

    Description

      MavenProject.getActiveProfiles() does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.

      This leads to preparation-builds of modules without the specified active profiles derived from their parents.

      Attachments

        Issue Links

        relates to

        Bug - A problem which impairs or prevents the functions of the product. MRELEASE-415 Plugin fails to activate profiles in submodules.

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MRELEASE-756 release:prepare ignores properties from settings.xml

        • Major - Major loss of function.
        • Closed

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            rfscholte Robert Scholte
            lcorneliussen Lars Corneliussen
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment