Github user talios commented on the issue:
https://github.com/apache/maven/pull/70
@barthel Maybe, I'm running 3.4.0-SNAPSHOTs anyway, and might pull in your
PR to play with and see if it helps with what I'm doing. My currently problem
is that IntelliJ IDEA doesn't
Github user talios commented on the issue:
https://github.com/apache/maven/pull/70
@barthel is there an example anywhere of using this? I have a project
(custom lifecycle extension) myself where I think utilizing this will actually
make what I'm doing much easier, nicer
Github user talios commented on the pull request:
https://github.com/apache/maven/pull/21#issuecomment-46105389
wow - what the hell happened to the formatting here?
@jvanzyl said in one part "In the case of my current setup we simply
disallow SNAPSHOTs entirely."
Github user talios commented on the pull request:
https://github.com/apache/maven/pull/21#issuecomment-46076519
Interesting about the version range changes in aether there - whilst the
[2.2.*] range is nice, that doesn't offer SNAPSHOT exclusion - unless the
`VersionFilter` is
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
Github user talios commented on the pull request:
https://github.com/apache/maven/pull/21#issuecomment-45968040
How will this affect the maven-release-plugin's release:prepare-with-pom
goal? Will the parent version reference be automatically resolved and written
correctly, or wi
