Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/21#issuecomment-45974252
I have done several releases using 'release:prepare release:perform' with a
parent version range in use. The release plugin won't write the resolved parent
version to the released pom. That's intentional. It shouldn't. The parent
version range should be deployed as is. That's the reason the build will fail
if a parent version range is in use and a child module uses a version
expression or inherits the version from the parent. As soon as a parent version
range is in use, <version>${some.expression}</version> and not providing a
version element will not be supported in child modules. In addition, the parent
version range is checked to contain an upper bound so that it is not possible
to e.g. deploy an artifact to central using a parent version range which is not
upper-bounded.
ITs are working with the patch applied. I will provide a pull-request
against 'maven-integration-testing' as soon as I finish some ITs.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
