Skip to content

Conversation

@anukalp2804
Copy link
Contributor

This PR is part of Issue #1436 – Document Deprecations and improves the
documentation of deprecated parameters in the Maven Release Plugin.

  • Updated documentation for generateReleasePoms in PrepareReleaseMojo
    to explain why it is deprecated and recommend using
    release:prepare-with-pom instead.
  • Updated documentation for useReleaseProfile in PerformReleaseMojo
    to clarify that the Maven super POM release-profile is being removed
    and projects should rely on explicit project-defined release profiles.
  • No functional behavior changes.
  • Build successfully verified using mvn clean install.

Reference: #1436
/cc @elharo

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Your pull request should address just one issue, without pulling in other changes.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Each commit in the pull request should have a meaningful subject line and body.
    Note that commits might be squashed by a maintainer on merge.
  • Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
    This may not always be possible but is a best-practice.
  • Run mvn verify to make sure basic checks pass.
    A more thorough check will be performed on your pull request automatically.
  • You have run the integration tests successfully (mvn -Prun-its verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

Clarified that getModel() is a temporary legacy accessor and will be
removed once transform() is fully implemented. Added guidance to rely
on the extract -> transform -> load pipeline instead.
* true, which activates the profile "<code>release-profile</code>" as inherited from
* <a href="/ref/3.8.5/maven-model-builder/super-pom.html">the super pom</a>.
* Whether to use the default {@code release-profile} from the Maven
* super POM (Maven 2 and 3), which adds sources and javadocs to the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

delete (Maven 2 and 3),

* Controls whether the plugin should generate release POMs during the
* prepare phase.
*
* @deprecated This flag is no longer the preferred way to perform a
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

delete "This flag is no longer the preferred way to perform a release."

* prepare phase.
*
* @deprecated This flag is no longer the preferred way to perform a
* release. Use the dedicated {@code release:prepare-with-pom}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just "Use the {@code release:prepare-with-pom} goal instead."

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the review. I’ve updated the Javadoc as requested.

Improved documentation for deprecated parameters:
- generateReleasePoms: explained deprecation and pointed users to
  release:prepare-with-pom.
- useReleaseProfile: clarified that the super POM release-profile is
  being removed and projects should rely on explicit profiles instead.

No functional changes. Build verified.
@anukalp2804 anukalp2804 force-pushed the doc-deprecations-release-plugin branch from 56e7efd to 28abf56 Compare January 8, 2026 14:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants