Github user talios commented on the pull request:
https://github.com/apache/maven/pull/21#issuecomment-45975916
With regards to `release:prepare` I agree, but here I'm talking about
release:prepare-with-pom which generates a "resolved pom" in relation to
version ranges, in that instance - we should be consistent.
It also worries me slightly that with all the existing issues with version
ranges, introduces magical "upper bounds checks in parents only" will cause
issues - as that somewhat implies we're not got any centralised rules around
range resolution ( this is a contentious issue as there is a long standing
issue wanting -SNAPSHOTs to be excluded from ranges, but only under certain
circumstances - i.e. integration testing may want SNAPSHOTs, but compilation
should nominally only use released artifacts ).
Ideally - this could be solved as part of the POM 5 change, if `<version/>`
had for instance a `includeSnapshots` or `allowOpenRange` attribute or
something - and force the _default_ to be no SNAPSHOTs, no open ranges.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
