From 391c92e43ccae98835dbdadd60b86afcd29bbe58 Mon Sep 17 00:00:00 2001 From: David Groomes Date: Mon, 10 May 2021 18:29:47 -0500 Subject: [PATCH] Upgrade to Gradle 7.0.1 Consolidate markdown files (stop usign docs/) Intent to make projects standalone. --- docs/README.md => README.md | 21 +++++++++++++++++++++ docs/CONTRIBUTING.md | 22 ---------------------- gradle/wrapper/gradle-wrapper.properties | 2 +- 3 files changed, 22 insertions(+), 23 deletions(-) rename docs/README.md => README.md (51%) delete mode 100644 docs/CONTRIBUTING.md diff --git a/docs/README.md b/README.md similarity index 51% rename from docs/README.md rename to README.md index 877dd35..296cf4c 100644 --- a/docs/README.md +++ b/README.md @@ -43,6 +43,27 @@ Instructions: General clean-ups, changes and things I wish to implement for this project: +* Make the sub-projects completely standalone and adhere to the convention I have in my other playground repos. +* Add a stub with a custom handler that uses custom Java code to respond to the request. * Create a WireMock-in-Docker example * DONE create a sub-project that declares dependency constraint versions and which will be used as a `platform(...)` from the other projects. For details of this feature, see the [Gradle docs about "platform"](https://docs.gradle.org/current/userguide/platforms.html) + +## Notes + +* Create a JDK Flight Recording + * (see `java` options at and scroll down to `-XX:StartFlightRecording`) + * For the `programmatic` program: + * Build the distribution with `./gradlew programmatic:installDist` + * Set the JRE options with `export PROGRAMMATIC_OPTS="-XX:StartFlightRecording,dumponexit=true"` + * Run the program with `programmatic/build/install/programmatic/bin/programmatic` + * For the `standalone` program: + * Build the distribution with `./gradlew standalone:installDist` + * Set the JRE options with `export STANDALONE_OPTS="-XX:StartFlightRecording,dumponexit=true"` + * Run the program with `standalone/build/install/standalone/bin/standalone` + * After the program exits, the .jfr file will be captured. Visualize it using Mission Control + * Clone Mission Control and build it + * You must run it with a JDK 8 (and it must be installed at `/Library/Java/JavaVirtualMachines...` for some reason. I couldn't get an SDKMAN installed Java to work) + * E.g. `JAVA_HOME=/Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/ target/products/org.openjdk.jmc/macosx/cocoa/x86_64/JDK\ Mission\ Control.app/Contents/MacOS/jmc -vm $JAVA_HOME/bin` +* Can we run WireMock on Graal? If Jetty can run on Graal, then WireMock should be pretty easy to run on Graal. See an + example for running Jetty on Graal at diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md deleted file mode 100644 index fb951d8..0000000 --- a/docs/CONTRIBUTING.md +++ /dev/null @@ -1,22 +0,0 @@ -# Contributing - -To contribute, first see the project page . - -## Notes - -* Create a JDK Flight Recording - * (see `java` options at and scroll down to `-XX:StartFlightRecording`) - * For the `programmatic` program: - * Build the distribution with `./gradlew programmatic:installDist` - * Set the JRE options with `export PROGRAMMATIC_OPTS="-XX:StartFlightRecording,dumponexit=true"` - * Run the program with `programmatic/build/install/programmatic/bin/programmatic` - * For the `standalone` program: - * Build the distribution with `./gradlew standalone:installDist` - * Set the JRE options with `export STANDALONE_OPTS="-XX:StartFlightRecording,dumponexit=true"` - * Run the program with `standalone/build/install/standalone/bin/standalone` - * After the program exits, the .jfr file will be captured. Visualize it using Mission Control - * Clone Mission Control and build it - * You must run it with a JDK 8 (and it must be installed at `/Library/Java/JavaVirtualMachines...` for some reason. I couldn't get an SDKMAN installed Java to work) - * E.g. `JAVA_HOME=/Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/ target/products/org.openjdk.jmc/macosx/cocoa/x86_64/JDK\ Mission\ Control.app/Contents/MacOS/jmc -vm $JAVA_HOME/bin` -* Can we run WireMock on Graal? If Jetty can run on Graal, then WireMock should be pretty easy to run on Graal. See an - example for running Jetty on Graal at diff --git a/gradle/wrapper/gradle-wrapper.properties b/gradle/wrapper/gradle-wrapper.properties index 442d913..e5338d3 100644 --- a/gradle/wrapper/gradle-wrapper.properties +++ b/gradle/wrapper/gradle-wrapper.properties @@ -1,5 +1,5 @@ distributionBase=GRADLE_USER_HOME distributionPath=wrapper/dists -distributionUrl=https\://services.gradle.org/distributions/gradle-6.8.3-bin.zip +distributionUrl=https\://services.gradle.org/distributions/gradle-7.0.1-bin.zip zipStoreBase=GRADLE_USER_HOME zipStorePath=wrapper/dists