Page History

...

• Timestamps:
  • Timestamps in ZIP/JAR files: file last modification time/date in central directory and file entry headers + possible optional fields "X5455_ExtendedTimestamp" (PLEXUS-ARCHIVER-48121)
  • Timestamp in pom.properties generated by maven-archiver (MSHARED-494 )
  • Timestamp in plugin.xml and plugin-help.xml descriptors generated by maven-plugin-tools-generator (MPLUGIN-326 )
  • Timestamp in MANIFEST.MF (Bnd-LastModified) generated by Felix maven-bundle-plugin
  • 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:
  • UID/GID in tar file entries
  • Username in MANIFEST.MF (Built-By) generated by maven-archiver (MSHARED-661 )
• 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)
  • Order of goals in plugin.xml generated by maven-plugin-tools (MPLUGIN-261)
  • Order of the methods of the ObjectFactory.java file generated by JAXB/xjc (JAXB-598)
  • Order of components in META-INF/plexus/components.xml generated by plexus metadata (issue #8)
• 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)
  • exact Maven version used to build in META-INF/.../pom.properties generated by maven-archiver (MSHARED-800)

...