description: Request a package be removed from the documentation site (pkg.go.dev)
title: "x/pkgsite: package removal request for [type path here]"
labels: ["pkgsite/package-removal"]
body:
  - type: markdown
    attributes:
      value: "Please answer these questions before submitting your issue. Thanks!"
  - type: input
    id: package-path
    attributes:
      label: "What is the path of the package that you would like to have removed?"
      description: |

If you experience or witness unacceptable behavior — or have any other concerns — please report it by
emailing [******@****.***][codeofconduct_at]. All reports will be handled with
discretion.

In your report please include:

 * Your contact information.
 * Names (real, nicknames, or pseudonyms) of any individuals involved. If there are additional
   witnesses, please include them as well.

Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.

Also, please include a link to a GraphDef or the model if possible.

**Any other info / logs**

Include any logs or source code that would be helpful to diagnose the problem.
If including tracebacks, please include the full traceback. Large logs and files

    // operation) no overload can be selected in phase 1.  and in phase 2 it is ambiguous since it
    // matches with the second parameter being boxed and without it being boxed.  The cast to Object
    // avoids this.
    checkState(aBoolean, "", aBoolean ? "" : anInt, (Object) anInt);

    // ambiguous without the .booleanValue() call since the boxing forces us into phase 2 resolution
    short s = 2;

    // operation) no overload can be selected in phase 1.  and in phase 2 it is ambiguous since it
    // matches with the second parameter being boxed and without it being boxed.  The cast to Object
    // avoids this.
    checkState(aBoolean, "", aBoolean ? "" : anInt, (Object) anInt);

    // ambiguous without the .booleanValue() call since the boxing forces us into phase 2 resolution
    short s = 2;

<!--
Please open pull requests against one of the following branches:

- master — default target for all changes (new features + bug fixes).  
  If the change should also go to maven-4.0.x, request a backport in the PR.

- maven-3.10.x — target for 3.x changes (new features + bug fixes).  
  If the change should also go to maven-3.9.x, request a backport in the PR.
  maven-3.9.x should receive only serious bug fixes, as it is approaching EOL.

 *
 * <p>Key features include:</p>
 * <ul>
 *   <li>Build lifecycle execution control</li>
 *   <li>Project-specific configuration</li>
 *   <li>Goal execution and phase mapping</li>
 *   <li>Multi-module build coordination</li>
 * </ul>
 *
 * @see org.apache.maven.api.cli.Tools#MVN_CMD
 * @see org.apache.maven.api.cli.Tools#MVN_NAME
 * @since 4.0.0
 */

import java.util.Map;

import org.apache.maven.api.model.InputLocation;
import org.apache.maven.api.model.InputSource;
import org.apache.maven.api.model.Model;
import org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException;
import org.junit.jupiter.api.Test;

class StringSearchModelInterpolatorTest {

    @Test
    void interpolate() throws ModelInterpolationException, InitializationException {

    id: jobs
    attributes:
      label: Which jobs are flaking?
      description: |
        Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI.
        Links to go.k8s.io/triage and/or links to specific failures in spyglass are appreciated.

 */
package org.apache.maven.lifecycle.mapping;

import java.util.List;

import org.apache.maven.api.xml.XmlNode;
import org.apache.maven.model.Dependency;

/**
 * Mojo (plugin goal) binding to a lifecycle phase.
 *
 * @see LifecyclePhase
 */
public class LifecycleMojo {

    private String goal;
    private XmlNode configuration;
    private List<Dependency> dependencies;

    public String getGoal() {