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

["Ceki Gülcü (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MJAR-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ceki Gülcü updated MJAR-285:
----------------------------
    Description: 
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?

  was:
Hello,

It looks like the addition of compressed files under  META-INF/versions/ or module-info.class does not use the project.build.outputTimestamp but the local time instead.

In any case, in logback's build,  {{META-INF/versions/9/module-info.class}} has a different timestamp than other files.

This prevents reproducible builds,


> 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)