Versions Compared

Old Version 41

changes.mady.by.user Herve Boutemy

Saved on

compared with

New Version 42

changes.mady.by.user Herve Boutemy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: maven-archiver work log

...

  • Timestamps:
    • Timestamp in pom.properties generated by maven-archiver (MSHARED-494 (tick))
    • Timestamp in plugin.xml and plugin-help.xml descriptors generated by maven-plugin-tools-generator (MPLUGIN-326 (tick))
    • Timestamp in MANIFEST.MF (Bnd-LastModified) generated by Felix maven-bundle-plugin
    • Timestamps in ZIP/JAR files: file last modification time/date in central directory and file entry headers + possible optional fields "X5455_ExtendedTimestamp" (PLEXUS-ARCHIVER-48)
    • Timestamps in generated javadoc HTML files (can be disabled with javadoc options "notimestamp" and "bottom")
    • Timestamps in bytecode generated from Groovy code (added by GroovyClassLoader.addTimeStamp())
  • Username:
    • Username in MANIFEST.MF (Built-By) generated by maven-archiver (MSHARED-661 (tick))
    • UID/GID in tar file entries
  • Ordering:
    • Order of the file entries in a ZIP/JAR file (depends on file system order)
    • Order of the entries in the MANIFEST (MSHARED-511 (tick))
    • Order of goals in plugin.xml generated by maven-plugin-tools (MPLUGIN-261(tick))
    • Order of the methods of the ObjectFactory.java file generated by JAXB/xjc (JAXB-598(tick))
    • Order of components in META-INF/plexus/components.xml generated by plexus metadata

...

  • Tools Versions:
    • exact JDK version used to build in MANIFEST.MF (Build-Jdk) generated by maven-archiver (MSHARED-797)
      Notice that keeping the major version of the JDK used still makes sense, since it has an influence on generated bytecode: with the same source code and defined -target version, javac from JDK 6, 7, 8, ... do not produce the same bytecode. If we want to isolate the generated binary from JDK used, the compiler used will have to not be javac provided by running JDK (see Using Non-Javac Compilers)
    • exact Maven version used to build in MANIFEST.MF (Created-By) generated by maven-archiver (MSHARED-799)

Line endings is also a problem, and even if we could force given line endings for build-generated text files (MANIFEST, pom.properties...), it would be hazardous to try to change the line endings of the resource files.

...

columns

MSHARED-796 (fixed in maven-archiver-3.4.0)

key
issue trackingdescription
MSHARED-661 (fixed in maven-archiver-3.4.0)

maven-archiver adds "Built-By: <username>" Manifest entry
this component is then used by many plugins that create archives

The entry was removed

Jira
serverASF JIRA

key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keymaven-archiver adds "Built-Jdk: <detailed java version>" Manifest entry: better replaced with "Built-Jdk: <java specification version>"
MSHARED-494 (fixed in maven-archiver 3.1.0)Timestamp in pom.properties 
Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b

MSHARED-505

support SOURCE_DATE_EPOCH environment variable or equivalent: see https://reproducible-builds.org/docs/timestamps/

sort zip entries to make zip entries order reproducible
MPLUGIN-261 (fixed in maven-plugin-plugin 3.3)generated plugin.xml is non-deterministic
MPLUGIN-326 (fixed in maven-plugin-plugin 3.5.1)Timestamp in plugin.xml and plugin-help.xml descriptors generated by maven-plugin-tools-generator
codehaus-plexus/plexus-archiver issue #48avoid timestamp issues in archives created by plexus-archiver (widely used in Maven plugins creating jar, zip, war, tar... archives)
codehaus-plexus/plexus-containers issue #8 (fixed in plexus-component-metadata 2.0.0)
sort components when generating META-INF/plexus/components.xml

...