[
https://issues.apache.org/jira/browse/MSHARED-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15230678#comment-15230678
]
Karl Heinz Marbaise edited comment on MSHARED-494 at 4/8/16 7:17 PM:
---------------------------------------------------------------------
FWIW, if MSHARED-505 is taken on, one could simply fix the timestamp in the
comment (although one still needs to circumvent {{store()}}) and leave the
current behavior as a often useful default. A changing timestamp is better than
no timestamp, IMHO.
was (Author: sewe):
FWIW, if SHARED-505 is taken on, one could simply fix the timestamp in the
comment (although one still needs to circumvent {{store()}}) and leave the
current behavior as a often useful default. A changing timestamp is better than
no timestamp, IMHO.
> Impossible to generate a reproducible build due to timestamp in pom.properties
> ------------------------------------------------------------------------------
>
> Key: MSHARED-494
> URL: https://issues.apache.org/jira/browse/MSHARED-494
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
> Affects Versions: maven-archiver-3.0.0
> Reporter: Emanuele Tagliaferri
> Priority: Minor
>
> Try to making a pom for do a reproducible build, meaning by reproducible
> build the ability to produce the exact same artifact (same checksum) starting
> from the same code, a two different times, i had some trouble with the files
> generated in: /META-INF/maven/groupId/artifactId/
> in the specific the /META-INF/maven/groupId/artifactId/pom.properties
> contains the timestamp.
> digging in the code in the class:
> http://svn.apache.org/viewvc/maven/shared/tags/maven-archiver-3.0.0/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java?revision=1708674&view=markup
> line 86
> is used the java.util.Properties#store which write the timestamp in any case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
