[jira] [Commented] (MJAR-300) maven jar plugin does not interpret build outputTimestamp correctly

[ https://issues.apache.org/jira/browse/MJAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832287#comment-17832287 ] Michael Osipov commented on MJAR-300: - Can we close this issue? > maven jar plugin does not interpret

[jira] [Commented] (MJAR-300) maven jar plugin does not interpret build outputTimestamp correctly

[ https://issues.apache.org/jira/browse/MJAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832006#comment-17832006 ] Henning Schmiedehausen commented on MJAR-300: - I ended up using the maven archiver parsing code

[jira] [Commented] (MJAR-300) maven jar plugin does not interpret build outputTimestamp correctly

[ https://issues.apache.org/jira/browse/MJAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831982#comment-17831982 ] Jorge Solórzano commented on MJAR-300: -- [~henning] Just as additional information: If you intend to

[jira] [Commented] (MJAR-300) maven jar plugin does not interpret build outputTimestamp correctly

[ https://issues.apache.org/jira/browse/MJAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816898#comment-17816898 ] Herve Boutemy commented on MJAR-300: Maven Archiver objective is done to zip content from disk, and

[jira] [Commented] (MJAR-300) maven jar plugin does not interpret build outputTimestamp correctly

[ https://issues.apache.org/jira/browse/MJAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816841#comment-17816841 ] Henning Schmiedehausen commented on MJAR-300: - Thanks for the response. This is not what I

[jira] [Commented] (MJAR-300) maven jar plugin does not interpret build outputTimestamp correctly

[ https://issues.apache.org/jira/browse/MJAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816837#comment-17816837 ] Herve Boutemy commented on MJAR-300: bq. What would be your recommendation? please try to use your

[jira] [Commented] (MJAR-300) maven jar plugin does not interpret build outputTimestamp correctly

[ https://issues.apache.org/jira/browse/MJAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816696#comment-17816696 ] Henning Schmiedehausen commented on MJAR-300: - [~hboutemy]  I looked at the code in

[jira] [Commented] (MJAR-300) maven jar plugin does not interpret build outputTimestamp correctly

[ https://issues.apache.org/jira/browse/MJAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816510#comment-17816510 ] Herve Boutemy commented on MJAR-300: we intentionally made the magic to have binary result independent

[jira] [Commented] (MJAR-300) maven jar plugin does not interpret build outputTimestamp correctly

[ https://issues.apache.org/jira/browse/MJAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816455#comment-17816455 ] Michael Osipov commented on MJAR-300: - I believe that there is a misunderstanding from your end.

[jira] [Commented] (MJAR-300) maven jar plugin does not interpret build outputTimestamp correctly

[ https://issues.apache.org/jira/browse/MJAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816452#comment-17816452 ] Henning Schmiedehausen commented on MJAR-300: - the fourth example just reinforces what I wrote:

[jira] [Commented] (MJAR-300) maven jar plugin does not interpret build outputTimestamp correctly

[ https://issues.apache.org/jira/browse/MJAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816451#comment-17816451 ] Henning Schmiedehausen commented on MJAR-300: - In your second example: 

[jira] [Commented] (MJAR-300) maven jar plugin does not interpret build outputTimestamp correctly

[ https://issues.apache.org/jira/browse/MJAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816386#comment-17816386 ] Michael Osipov commented on MJAR-300: - When {{TZ}} is consistently applied everything is fine:

[jira] [Commented] (MJAR-300) maven jar plugin does not interpret build outputTimestamp correctly

[ https://issues.apache.org/jira/browse/MJAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816383#comment-17816383 ] Michael Osipov commented on MJAR-300: - This is weird, needs more thought. One of the problems with the

[jira] [Commented] (MJAR-300) maven jar plugin does not interpret build outputTimestamp correctly

[ https://issues.apache.org/jira/browse/MJAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816369#comment-17816369 ] Henning Schmiedehausen commented on MJAR-300: - This is a major (borderline blocking) bug for me

[jira] [Commented] (MJAR-300) maven jar plugin does not interpret build outputTimestamp correctly

[ https://issues.apache.org/jira/browse/MJAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816368#comment-17816368 ] Henning Schmiedehausen commented on MJAR-300: - I can track this down to this line in

[jira] [Commented] (MJAR-300) maven jar plugin does not interpret build outputTimestamp correctly

[ https://issues.apache.org/jira/browse/MJAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816367#comment-17816367 ] Henning Schmiedehausen commented on MJAR-300: - repo: https://github.com/hgschmie/MJAR-300 >