The 2.5.X range of the assembly plugin combined with maven-filtering 1.3 has gotten ferociously good at preserving file attributes (unix mode bits and modification time), to the extent that it may have gotten /too/ good, since it can now filter a file for line endings/interpolation and still preserve all the original file attributes, whatever the source of the file (inside zip/jar/file system).
Hence we now have MASSEMBLY-734, which happens because semantically an interpolated file is /not/ the same as the original. So we have a few options: A) Always treat a potentially filtered file as a new file (change modification date, keep attributes of original) B) Treat file as changed if it was interpolated -but maybe not filtered for line endings (change modification date, keep attributes of original) C) Make a flag to use A but keep current behaviour if flag is false WDYT ? Kristian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
