[GR-42375] Introduce -H:±GenerateBuildArtifactsFile option.

[graalvmbot]

and deprecate .build_artifacts.txt files.

[fniephaus]

@jerboaa please feel free to take a look at this. We've decided to not include this in the build output JSON because the two files target different consumers: build output for monitoring, build artifacts for packaging tools.
Also note the new (internal) -H:BuildArtifactsJSON option only accepts a path and is inconsistent with -H:BuildOutputJSONFile, which also accepts a filename. I will share more details on how we plan to unified all of this within a public API in the future, would be great to get your feedback on that as well.

[jerboaa]

Looks fine to me.

[jerboaa]

Also note the new (internal) -H:BuildArtifactsJSON option only accepts a path and is inconsistent with -H:BuildOutputJSONFile, which also accepts a filename. I will share more details on how we plan to unified all of this within a public API in the future, would be great to get your feedback on that as well.

OK, looking forward to hear more about this. As long as we have a way of knowing what the produced output filename is (for -HBuildOutputJSONFile) this should be fine.

[fniephaus]

Thanks for the quick review.

As long as we have a way of knowing what the produced output filename is (for -HBuildOutputJSONFile) this should be fine.

Yes, although we probably won't allow users to customize the filename (easier to unify output and to match against corresponding schema), only the target directory can be changed.

[jerboaa]

Yes, although we probably won't allow users to customize the filename (easier to unify output and to match against corresponding schema), only the target directory can be changed.

Sure, as long as the file name is predictable, say build-output.json within a user-specified directory it would be fine for us. What would be inconvenient is if files end up containing random strings like timestamps or some such. Please consider that, thanks!

[fniephaus]

Please consider that, thanks!

Sure, will do. Thank you

[fniephaus]

Please feel free to take another look, @jerboaa:

• The option is now a boolean flag. Not sure whether it should be called -H:±BuildArtifacts, -H:±ReportBuildArtifacts, or something else?
• Paths are now relative again, using uri-reference, which seems to allow relative paths (see here)
• Since we couldn't identify any external dependents, I disabled the creation of the old file by default and added support for NATIVE_IMAGE_DEPRECATED_BUILD_ARTIFACTS_TXT=true as a temporary fallback

[jerboaa]

I'll take a look next week, thanks.