[
https://issues.apache.org/jira/browse/MARTIFACT-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17833464#comment-17833464
]
ASF GitHub Bot commented on MARTIFACT-59:
-----------------------------------------
rmannibucau commented on PR #30:
URL:
https://github.com/apache/maven-artifact-plugin/pull/30#issuecomment-2034028188
> see https://gist.github.com/hboutemy/cca5a94c6f7a9bc65023a31c31d3308f
You have the same error than me.
> I don't get what CLI command it is related to: mvn
-Dproject.nuild.outputTimestamp=set
> I'm trying to guess the problem
`mvn xxxx` no `-D`. The key point is that in the pom you have an
interpolated value. See
https://github.com/apache/maven-artifact-plugin/pull/30#issuecomment-2026810271
which explains it.
This kind of injected (=interpolated) value just fails exactly the same than
moditech in your example on both commands (first exit with status=0 but logs an
error which is wrong and second just fails).
> 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
>
> Goal is to not log
> {code:java}
> Reproducible Build not activated by project.build.outputTimestamp property:
> see https://maven.apache.org/guides/mini/guide-reproducible-builds.html {code}
> when the project is actually set but computed from another property and not
> fail (check mojo) when the setup is the same.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
