Thorsten Glaser created MRELEASE-1143:
-----------------------------------------
Summary: MRELEASE should be able to recognise and update
project.build.outputTimestamp in a profile
Key: MRELEASE-1143
URL: https://issues.apache.org/jira/browse/MRELEASE-1143
Project: Maven Release Plugin
Issue Type: Improvement
Reporter: Thorsten Glaser
Follow-up for: MRELEASE-1029
I have pretty much the same problem as the ASF has in MPOM-255 and MPOM-265: I
build a parent POM in a project, and I want that project's output to be
reproducible, but if I set `project.build.outputTimestamp` in the parent POM
itself's `<properties>`, all users inherit it. This is suboptimal (even if not
harmful), especially as users' `mvn artifact:check-buildplan` will now succeed
with merely...
{noformat}
[WARNING] <project.build.outputTimestamp> property is inherited, it should be
defined in pom.xml{noformat}
... instead of erroring out when a user does _not_ define it.
In my parent POM, I have already defined a profile `build-mvnparent` which I
enable when releasing the parent POM project itself, which defines a couple of
properties such as the copyright years which I also don't want users to inherit
by accident.
However, when I put the `project.build.outputTimestamp` property in there, not
only do I get `mvn artifact:check-buildplan` warnings about the property being
inherited when it's not (just pulled from a profile), but also does the
maven-release-plugin not update it when releasing.
I would request that this be fixed, so then the ASF and I could use the profile
method of defining this in the parent POM without all users of the
parent-POM-once-installed inheriting that value (while all other modules in the
same project that _installs_ the parent POM _do_ get it), and once it's fixed,
the `artifact:check-buildplan` be updated to recognise this situation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
