fixed timestamps come from reproducible builds, maven 3.10 has it enabled by default
https://maven.apache.org/docs/3.10.0/release-notes.html#notable-changes-in-maven-3-10-0 Wondering if something is reading jar metadata instead of asking the filesystem. Something to check before NB 32 since this should work IMO. Possibly the nbm plugin? -mbien On 10/10/26 10:12, Patrik Karlström via dev wrote: > I noticed some strange things this morning while working on an platform > application. > My changes would not show up, despite many clean and builds. Then I realized > I had to clear the cache, for every change. > Dates in my manifest were all set to 1980-02-01, so none of my builds became > newer than that. > > I think it's connected to me updating maven from 3.9.16 to 3.10.0 this > morning. > > Adding > <project.build.outputTimestamp>2026-10-10T12:00:00Z</project.build.outputTimestamp> > helped but I ended up reverting my maven update. > > Perhaps this is known already, just wanted you to know. :) > > /Patrik --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
