Invalid Timestamp Error when running Gradle tasks on generated project

[matrei]

Issue description

When generating a Grails 7.0.0 zip from https://start.grails.org and running for example bootRun, the following error occurs:

Execution failed for task ':processResources'.
> Invalid Timestamp -3600000 for 'file '/home/mattias/Downloads/httpclienttest/grails-app/conf/spring''.

Updating grails-app/conf/spring/resources.groovy fixes that.

Execution failed for task ':processResources'.
> Invalid Timestamp -3600000 for 'file '/home/mattias/Downloads/httpclienttest/grails-app/views/layouts''.

Updating grails-app/views/layouts/main.gsp fixes that.

[jdaugherty]

When builds are reproducible, the time component is manipulated in the jar file via the gradle property: https://docs.gradle.org/current/javadoc/org/gradle/api/tasks/bundling/AbstractArchiveTask.html#isPreserveFileTimestamps()

I'm guessing the templates inside of the jar file are being copied as-is without updating the time?

[jamesfredley]

@matrei What OS?

What did you update on these two files? I was not able to reproduce.

[matrei]

This is Linux. The funny thing is that if I use command line unzip it does not happen. Only when using Ark.

[jamesfredley]

I think the timestamps can be updated here. This is used by ZipCreateController to generate the zip file.

grails-core/grails-forge/grails-forge-core/src/main/java/org/grails/forge/io/ZipOutputHandler.java

Lines 80 to 88 in 7f9a2c0

	public void write(String path, Template contents) throws IOException {
	ZipArchiveEntry zipEntry = new ZipArchiveEntry(directory != null ? StringUtils.prependUri(directory, path) : path);
	if (contents.isExecutable()) {
	zipEntry.setUnixMode(UnixStat.FILE_FLAG | 0755);
	}
	zipOutputStream.putArchiveEntry(zipEntry);
	contents.write(zipOutputStream);
	zipOutputStream.closeArchiveEntry();
	}