}) {
    init {
        smokeBuildTypes.forEach(this::buildType)
    }

    companion object {
        /**
         * Specific builds shown under the "Smoke Test" subproject in Pull Request Feedback.
         */
        val pullRequestFeedbackSmokeBuilds: Set<SpecificBuild> =
            setOf(
                SpecificBuild.SmokeTestsMaxJavaVersion,
                SpecificBuild.ConfigCacheAndroidProjectSmokeTests,

  - type: textarea
    id: govulncheck-version
    attributes:
      label: govulncheck version
      description: What version of govulncheck are you using (`govulncheck -version`)?
      placeholder: |

        Filing feature requests is one of the most popular ways to contribute to Guava.


        Be aware, though: most feature requests are not accepted, even if they're suggested by
        a full-time Guava team member. [Feedback](https://stackoverflow.com/a/4543114) from our
        users indicates that they really appreciate Guava's high power-to-weight ratio. It's

    val uuid: String,
) {
    QUICK_FEEDBACK_LINUX_ONLY(
        "Quick Feedback - Linux Only",
        "Run checks and functional tests (embedded executer, Linux)",
        "QuickFeedbackLinuxOnly",
    ),
    QUICK_FEEDBACK("Quick Feedback", "Run checks and functional tests (embedded executer, Windows)", "QuickFeedback"),
    PULL_REQUEST_FEEDBACK("Pull Request Feedback", "Run various functional tests", "PullRequestFeedback"),
    READY_FOR_NIGHTLY(

 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.plugin.logging;

/**
 * This interface supplies the API for providing feedback to the user from the <code>Mojo</code>, using standard
 * <code>Maven</code> channels.<br>
 * There should be no big surprises here, although you may notice that the methods accept

community includes:

* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, and experiences
* Giving and gracefully accepting constructive feedback
* Accepting responsibility and apologizing to those affected by our mistakes,
  and learning from the experience
* Focusing on what is best not just for us as individuals, but for the
  overall community

import java.util.function.Supplier;

import org.apache.maven.api.annotations.Experimental;
import org.apache.maven.api.annotations.Provider;

/**
 * This interface supplies the API for providing feedback to the user from the {@code Mojo},
 * using standard Maven channels.
 * There should be no big surprises here, although you may notice that the methods accept

        Filing feature requests is one of the most popular ways to contribute to Guava.


        Be aware, though: most feature requests are not accepted, even if they're suggested by
        a full-time Guava team member. [Feedback](https://stackoverflow.com/a/4543114) from our
        users indicates that they really appreciate Guava's high power-to-weight ratio. It's

Framing rules make it impractical to implement http/2 correctly on a single blocking thread. The flow-control features introduce feedback between reads and writes, requiring writes to acknowledge reads and reads to throttle writes.

In OkHttp we expose a blocking API over a framed protocol. This document explains the code and policy that makes that work.

The difference between internal properties and experimental properties is the amount of publicity they are intended to receive.
If the intention is to gather user feedback on an early prototype, then the experimental property should be used.