GenerateMetadataTask introduction. (#686)

Created MetadataGenerationUtils utility class for operations shared by ContributionTask and GenerateMetadataTask.

Author: kimeta

docs/CONTRIBUTING.md

@@ -39,6 +39,18 @@ After it collects your answers, the task will:
 - generate metadata and store it in the proper location
 - ask you if you want to create a pull request, or you want to keep working on it locally
 
+If you already have the test project structure in this repository and need to generate or regenerate metadata, use the `generateMetadata` task:
+
+```shell
+./gradlew generateMetadata --coordinates=com.example:my-library:1.0.0
+```
+
+To change the user-code-filter used during collection, pass `--allowedPackages` with a comma-separated list of packages:
+
+```shell
+./gradlew generateMetadata --coordinates=com.example:my-library:1.0.0 --allowedPackages=com.example.pkg,org.acme.lib
+```
+
 ### Checklist
 In order to ensure that all contributions follow the same standards of quality we have devised a following list of requirements for each new added library.
 `org.example:library` project is also included as a template for new libraries.

docs/DEVELOPING.md

@@ -93,6 +93,19 @@ Each stage of the testing can be run with `-Pcoordinates=[group:artifact:version
 ./gradlew test -Pcoordinates=[group:artifact:version|k/n|all]
 ```
 
+### Generating Metadata
+
+Generates metadata for a single library coordinate. If `agentAllowedPackages` is provided, a new user-code-filter.json will be created or updated to include those packages.
+
+- `coordinates`: group:artifact:version (single coordinate only)
+- `agentAllowedPackages`: comma-separated package list; use `-` for none
+
+Examples:
+   ```console
+   ./gradlew generateMetadata -Pcoordinates=org.postgresql:postgresql:42.7.3
+   ./gradlew generateMetadata -Pcoordinates=org.postgresql:postgresql:42.7.3 --agentAllowedPackages=org.example.app,com.acme.service
+   ```
+
 ### Docker image vulnerability scanning
 
 1. Scan only images affected in a commit range:
@@ -136,6 +149,7 @@ These tasks support the scheduled workflow that checks newer upstream library ve
 - Format apply: `./gradlew spotlessApply`
 - Pull images (single lib): `./gradlew pullAllowedDockerImages -Pcoordinates=[group:artifact:version|k/n|all]`
 - Check metadata (single lib): `./gradlew checkMetadataFiles -Pcoordinates=[group:artifact:version|k/n|all]`
+- Generate metadata (single lib): `./gradlew generateMetadata -Pcoordinates=group:artifact:version`
 - Test (single lib): `./gradlew test -Pcoordinates=[group:artifact:version|k/n|all]`
 - Scan changed Docker images: `./gradlew checkAllowedDockerImages --baseCommit=<sha1> --newCommit=<sha2>`
 - Scan all Docker images: `./gradlew checkAllowedDockerImages`

tests/tck-build-logic/src/main/groovy/org.graalvm.internal.tck-harness.gradle

@@ -17,6 +17,7 @@ import org.graalvm.internal.tck.MetadataFilesCheckerTask
 import org.graalvm.internal.tck.DockerUtils
 import org.graalvm.internal.tck.ScaffoldTask
 import org.graalvm.internal.tck.GrypeTask
+import org.graalvm.internal.tck.GenerateMetadataTask
 import org.graalvm.internal.tck.TestedVersionUpdaterTask
 import org.graalvm.internal.tck.harness.tasks.TestInvocationTask
 import org.graalvm.internal.tck.harness.tasks.CheckstyleInvocationTask
@@ -321,3 +322,9 @@ tasks.register("contribute", ContributionTask.class) { task ->
     task.setDescription("Generates metadata and prepares pull request for contibuting on metadata repository based on provided tests.")
     task.setGroup(METADATA_GROUP)
 }
+
+// gradle generateMetadata --coordinates=<maven-coordinates> [or -Pcoordinates=<maven-coordinates>] --agentAllowedPackages=<comma-separated list of packages>
+tasks.register("generateMetadata", GenerateMetadataTask.class) { task ->
+    task.setDescription("Generates metadata based on provided tests.")
+    task.setGroup(METADATA_GROUP)
+}