You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2021/07/13 08:19:00 UTC
[jira] [Commented] (MNG-6754) Set the same timestamp in multi
module builds
[ https://issues.apache.org/jira/browse/MNG-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379716#comment-17379716 ]
Michael Osipov commented on MNG-6754:
-------------------------------------
Fixed with [a3907fcb2b541d80852611b68494965f10b828f2|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=a3907fcb2b541d80852611b68494965f10b828f2] for {{maven-3.8.x}} branch.
> Set the same timestamp in multi module builds
> ---------------------------------------------
>
> Key: MNG-6754
> URL: https://issues.apache.org/jira/browse/MNG-6754
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories, Deployment
> Affects Versions: 3.6.3
> Reporter: Michael Angstadt
> Assignee: Michael Osipov
> Priority: Minor
> Fix For: 3.8.2, 4.0.0, 4.0.0-alpha-1
>
>
> When multi module snapshots are built using Maven, the version timestamp may be different for each module. This makes it difficult to quickly reference a historical snapshot of a multi module project, which is something we might do when determining when a bug was introduced.
> [This Stack Overflow question|https://stackoverflow.com/q/45629816/2048802] provides a good example of the problem. [The accepted answer|https://stackoverflow.com/a/45715820/2048802] seems like a reasonable solution, but does not appear to work. [Looking at the code|https://github.com/apache/maven/blob/d9a0eee7fe2e2b1d77e59cf5bc772e758d29e47d/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/RemoteSnapshotMetadata.java#L85], there does not appear to be a way to override the timestamp.
> Please add a way to use a consistent timestamp for all modules in a build.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)