Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Respect the processParent setting by introducing a new base class #289

Closed

Conversation

adamvoss
Copy link

@adamvoss adamvoss commented Jul 1, 2018

Respect the processParent setting by introducing a new base class.

Fixes #288 (UseNextReleasesMojo). Also, fixes an analogous bug in ForceReleasesMojo, UseDepVersionMojo, UseNextReleasesMojo, UseNextSnapshotsMojo, and UseNextVersionsMojo

The other existing Mojos that were not modified have their own parent-handling functionality except for CompareDependenciesMojo and UpdatePropertiesMojo where the setting still has no effect.

@adamvoss adamvoss force-pushed the respect-update-parent-setting branch 2 times, most recently from 5efe092 to ab3ea44 Compare July 2, 2018 00:12
@jdileonardo
Copy link
Contributor

I think i'm responsible for some of the other "parentProcessing" Mojo's.

One thing i noticed recently, is that if you try to "processParent" but you have no snapshot dependencies, it skips the whole operation. Something i'll have to address, and something to double check works for your change as well :)

@nickgr6
Copy link

nickgr6 commented Jan 3, 2019

Is there any reason why this fix is not merged yet?

Will this change also fix my issue regarding updating versions (versions:update-properties), in a property when the property is defined in the parent POM, of a project?

My project structure:

  • moduleA
    -- pom.xml (uses property from project/pom.xml as dependency
  • moduleB
    -- pom.xml (uses property from project/pom.xml as dependency
  • pom.xml - defines the version as property

Command which doesn't update the parent pom:
mvn org.codehaus.mojo:versions-maven-plugin:update-properties -Dincludes=nl.eleven:the-artifact-id:*:3.1.24 -DprocessParent=true -DallowSnapshots=false -DgenerateBackupPoms=false

There is a higher version (3.1.26) and it does work if a move the property to the poms of moduleA and moduleB (but I don't want to duplicate these versions..)

@DiJu519 any updates regarding this issue?

@github-actions
Copy link

This PR is stale because it has been open 365 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the Stale label Jun 10, 2021
@github-actions github-actions bot closed this Jul 11, 2021
@slachiewicz slachiewicz removed the Stale label Oct 10, 2021
@slachiewicz slachiewicz reopened this Oct 10, 2021
andrzejj0 added a commit to andrzejj0/versions-maven-plugin that referenced this pull request Nov 9, 2022
Also:
- added failIfNotReplaced to ForceReleasesMojo as a first steps towards converging with UseReleasesMojo
- added unit tests and integration tests
- some refactoring
andrzejj0 added a commit to andrzejj0/versions-maven-plugin that referenced this pull request Nov 10, 2022
Also:
- added failIfNotReplaced to ForceReleasesMojo as a first steps towards converging with UseReleasesMojo
- enhanced documentation on UseReleasesMojo#allowRangeMatching
- streamlined UseReleasesMojo in order to converge it with ForceReleasesMojo and then fold further with other similar mojos
- added unit tests and integration tests
- some refactoring
andrzejj0 added a commit to andrzejj0/versions-maven-plugin that referenced this pull request Nov 10, 2022
Also:
- added failIfNotReplaced to ForceReleasesMojo as a first steps towards converging with UseReleasesMojo
- enhanced documentation on UseReleasesMojo#allowRangeMatching
- streamlined UseReleasesMojo in order to converge it with ForceReleasesMojo and then fold further with other similar mojos
- added unit tests and integration tests
- some refactoring
andrzejj0 added a commit to andrzejj0/versions-maven-plugin that referenced this pull request Nov 11, 2022
Also:
- added failIfNotReplaced to ForceReleasesMojo as a first steps towards converging with UseReleasesMojo
- enhanced documentation on UseReleasesMojo#allowRangeMatching
- streamlined UseReleasesMojo in order to converge it with ForceReleasesMojo and then fold further with other similar mojos
- added unit tests and integration tests
- some refactoring
andrzejj0 added a commit to andrzejj0/versions-maven-plugin that referenced this pull request Nov 11, 2022
Also:
- added failIfNotReplaced to ForceReleasesMojo as a first steps towards converging with UseReleasesMojo
- enhanced documentation on UseReleasesMojo#allowRangeMatching
- streamlined UseReleasesMojo in order to converge it with ForceReleasesMojo and then fold further with other similar mojos
- added unit tests and integration tests
- some refactoring
andrzejj0 added a commit to andrzejj0/versions-maven-plugin that referenced this pull request Nov 11, 2022
Also:
- added failIfNotReplaced to ForceReleasesMojo as a first steps towards converging with UseReleasesMojo
- enhanced documentation on UseReleasesMojo#allowRangeMatching
- streamlined UseReleasesMojo in order to converge it with ForceReleasesMojo and then fold further with other similar mojos
- added unit tests and integration tests
- some refactoring
andrzejj0 added a commit to andrzejj0/versions-maven-plugin that referenced this pull request Nov 11, 2022
Also:
- added failIfNotReplaced to ForceReleasesMojo as a first steps towards converging with UseReleasesMojo
- enhanced documentation on UseReleasesMojo#allowRangeMatching
- streamlined UseReleasesMojo in order to converge it with ForceReleasesMojo and then fold further with other similar mojos
- added unit tests and integration tests
- some refactoring
andrzejj0 added a commit to andrzejj0/versions-maven-plugin that referenced this pull request Nov 11, 2022
Also:
- added failIfNotReplaced to ForceReleasesMojo as a first steps towards converging with UseReleasesMojo
- enhanced documentation on UseReleasesMojo#allowRangeMatching
- streamlined UseReleasesMojo in order to converge it with ForceReleasesMojo and then fold further with other similar mojos
- added unit tests and integration tests
- some refactoring
andrzejj0 added a commit to andrzejj0/versions-maven-plugin that referenced this pull request Nov 13, 2022
Also:
- added failIfNotReplaced to ForceReleasesMojo as a first steps towards converging with UseReleasesMojo
- enhanced documentation on UseReleasesMojo#allowRangeMatching
- streamlined UseReleasesMojo in order to converge it with ForceReleasesMojo and then fold further with other similar mojos
- added unit tests and integration tests
- some refactoring
andrzejj0 added a commit to andrzejj0/versions-maven-plugin that referenced this pull request Nov 16, 2022
Also:
- added failIfNotReplaced to ForceReleasesMojo as a first steps towards converging with UseReleasesMojo
- enhanced documentation on UseReleasesMojo#allowRangeMatching
- streamlined UseReleasesMojo in order to converge it with ForceReleasesMojo and then fold further with other similar mojos
- added unit tests and integration tests
- some refactoring
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.

use-next-releases does not respect processParent setting
4 participants