[
https://issues.apache.org/jira/browse/MARTIFACT-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17830384#comment-17830384
]
ASF GitHub Bot commented on MARTIFACT-59:
-----------------------------------------
rmannibucau commented on PR #30:
URL:
https://github.com/apache/maven-artifact-plugin/pull/30#issuecomment-2017402158
Goal is really to enable the value to be a property from the project but not
hardcoded.
Typically it is injected from a plugin in initialize phase (git commit id
plugin for ex).
High level here the issue with current option:
* hardcoded in the pom breaks several use cases until you make it moving
everytime you change something in the project (or part of it - often the
frontend but also the backend in some cases). Assuming you accept it - which I
think is already not good, you have conflict issues very often with concurrent
PR,
* System property reduces reproducibility since you need to ensure to pass
the same value between builds which is manual so will fail (Murphy's law)
* Ultimately there are multiple plugins able to inject this date from a
computed criteria - most of the time using SCM - so we should be able to use it
by design.
This PR just tries to make last option not emitting a warning.
> artifact plugin should tolerate injected project.build.outputTimestamp
> ----------------------------------------------------------------------
>
> Key: MARTIFACT-59
> URL: https://issues.apache.org/jira/browse/MARTIFACT-59
> Project: Maven Artifact Plugin
> Issue Type: Improvement
> Reporter: Romain Manni-Bucau
> Priority: Minor
> Labels: pull-request-available
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
