You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (Jira)" <ji...@apache.org> on 2022/01/28 06:53:00 UTC

[jira] [Commented] (MJAR-285) versioned files do not use project.build.outputTimestamp

    [ https://issues.apache.org/jira/browse/MJAR-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17483596#comment-17483596 ] 

Herve Boutemy commented on MJAR-285:
------------------------------------

this is known and tracked as MJAR-275, at least the module-info.class part (and not easy to fix given it relies on JDK's jar command...)

> versioned files do not use project.build.outputTimestamp  
> ----------------------------------------------------------
>
>                 Key: MJAR-285
>                 URL: https://issues.apache.org/jira/browse/MJAR-285
>             Project: Maven JAR Plugin
>          Issue Type: Sub-task
>    Affects Versions: 3.2.2
>            Reporter: Ceki Gülcü
>            Priority: Major
>
> Hello,
> It looks like the addition of compressed files under  META-INF/versions/ or module-info.class does not use the value of {{project.build.outputTimestamp}} but the local time instead.
> In any case, in logback project's build,  {{META-INF/versions/9/module-info.class}} has a different timestamp than other files.
> This prevents reproducible builds.
> Could you please have a look?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)