<properties>
    <filter.resources>true</filter.resources>
    <releasesEnabled>true</releasesEnabled>
  </properties>

  <repositories>
    <repository>
      <id>maven-core-it</id>
      <url>file:///${basedir}/repo</url>
      <releases>
        <!-- That's the boolean POM field we would like to interpolate -->
        <enabled>${releasesEnabled}</enabled>
      </releases>
    </repository>
  </repositories>

  <build>

        It does not affect the behaviour of proxy.golang.org or the go command.
        Instead we recommend using the retract directive which will be processed by all 3 of the above.

        If you have deleted your repo, please recreate it and publish a retraction.

        Retracting a module version involves adding a retract directive to your go.mod file and publishing a new version.

          close-pr-message: "This PR was closed because it has been inactive for 14 days since being marked as stale. Please reopen if you'd like to work on this further."
          repo-token: ${{ secrets.GITHUB_TOKEN }}
      - name: Contribution issues
        uses: actions/stale@5f858e3efba33a5ca4407a664cc011ad407f2008 # v10.1.0
        with:

history. You can see a summary of contributions at
https://github.com/google/guava/graphs/contributors. However, Git history
over-counts some people's contributions because they were responsible for
mirroring out changes from our internal repo.

This files serves mainly to credit people who have not received proper credit
in the Git history.

Doug Lea, author of some concurrency libraries

  <artifactId>b</artifactId>
  <version>0.1</version>
  <packaging>jar</packaging>

  <distributionManagement>
    <repository>
      <id>maven-core-it</id>
      <url>file:///${basedir}/repo</url>
    </repository>
  </distributionManagement>

  <properties>
    <maven.test.skip>true</maven.test.skip>
    <updateReleaseInfo>true</updateReleaseInfo>
  </properties>

  <build>
    <resources>

  <artifactId>d</artifactId>
  <version>0.1</version>
  <packaging>jar</packaging>

  <distributionManagement>
    <repository>
      <id>maven-core-it</id>
      <url>file:///${basedir}/repo</url>
    </repository>
  </distributionManagement>

  <properties>
    <maven.test.skip>true</maven.test.skip>
    <updateReleaseInfo>true</updateReleaseInfo>
  </properties>

  <build>
    <resources>

    runs-on: ubuntu-latest
    env:
      ACTIONS_STEP_DEBUG: true
    steps:
    - name: Close Stale Issues
      uses: actions/stale@v8
      with:
        repo-token: ${{ secrets.GITHUB_TOKEN }}

      issues: write
      pull-requests: read
    if: |
      github.repository == 'tensorflow/tensorflow' &&
      startsWith(github.event.head_commit.message, 'Rollback of PR #')
    steps:
      - name: Checkout repo
        uses: actions/checkout@1af3b93b6815bc44a9784bd300feb67ff0d1eeb3 # v6.0.0
      - name: Create a new Github Issue
        uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8.0.0
        with:

                .artifactId("foo")
                .repositories(Collections.singletonList(org.apache.maven.api.model.Repository.newBuilder()
                        .url("file://localhost/${basedir}/temp-repo")
                        .build()))
                .build());

        ModelInterpolator interpolator = createInterpolator();

        final SimpleProblemCollector collector = new SimpleProblemCollector();

            if (EventType.ARTIFACT_DESCRIPTOR_MISSING.equals(evt.getType())) {
                assertEquals(
                        "Could not find artifact org.apache.maven.its:dep-mng5459:pom:0.4.0-20130404.090532-2 in repo ("
                                + newTestRepository().getUrl() + ")",
                        evt.getException().getMessage());
                missingArtifactDescriptor = true;
            }
        }