> > I've just opened a PR with this change ( > https://github.com/apache/wicket/pull/758). I don't think this change > will be problematic, but as it only really influences the release builds, > it's hard to test its effect without doing an actual release. >
It turned out that maven-bundle-plugin doesn't set these timestamps at all. The fix was to switch back to jar-packaging and use the maven-bundle-plugin to generate the manifest only. The jar is now again built by the maven-jar-plugin, which does respect project.build.outputTimestamp. The contents of the manifest.mf is equivalent (not identical, because the entries are sorted differently and the line length is different), so I think this change is ok. Best regards, Emond
