[
https://issues.apache.org/jira/browse/MARTIFACT-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17832905#comment-17832905
]
ASF GitHub Bot commented on MARTIFACT-59:
-----------------------------------------
hboutemy commented on PR #30:
URL:
https://github.com/apache/maven-artifact-plugin/pull/30#issuecomment-2030164494
> > FYI, moditect uses the git commit strategy and there is no issue for
them
> Cause they don't use any of artifact plugin nor use it in the root pom
otherwise it is there for them too ;).
wrong, they use everything, and it works: I still don't get what needs to be
changed in maven-artifact-plugin
> So my proposal would be:
> ...
this proposal is not in the hands of the maven-artifact-plugin, but Maven 5
(new element in `<build>`) and decision to make Maven core depend on Git or
not: a discussion for Maven core in the mailing list
> 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)
