Maven Release Plugin
  1. Maven Release Plugin
  2. MRELEASE-688

Release a project and all its snapshot dependencies, without an aggregator

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Auto Closed
    • Affects Version/s: 2.1
    • Fix Version/s: None
    • Component/s: perform, prepare
    • Labels:
      None

      Description

      Hi all,

      We are looking for a way to perform a release on a project and all its snapshot dependencies (internal dependencies only).

      Using a pom aggregator and $

      {project.version}

      in dependencyMgmt for all internal dependencies allows such a release in "one click", but the drawback is we have to regroup projects within this aggregator, according to the dependency graph.

      We would like to be able to do the same thing, but without having to use an aggregator, that in some way add another link between projects than their dependencies.
      The process would be the same than with an aggregator, but instead of building a maven reactor with modules, it would be done among snapshot dependencies.
      Scm element is set in each dependency's pom, so maven-release-plugin could find where sources are, and release them.

      Could maven-release-plugin manage this with a new parameter ? (releaseSnapshotDependencies=true for example)

      We already had some posts here: http://maven.40175.n5.nabble.com/Relesa-a-project-and-all-its-snapshot-dependencies-without-an-aggregator-td4527536.html

      Thx
      Maxime

        Activity

        Hide
        Michael Osipov added a comment -

        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.

        Show
        Michael Osipov added a comment - 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.

          People

          • Assignee:
            Unassigned
            Reporter:
            Maxime Lemanissier
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development