<groupId>com.example.group</groupId>
  <artifactId>testinvalidpom</artifactId>
  <version>0.0.1-SNAPSHOT</version>

  <build>
    <pluginManagement>
      <plugins>
        <plugin>
          <groupId>the.group.id</groupId>
          <artifactId>the.artifact</artifactId>
          <version/>
        </plugin>
      </plugins>
    </pluginManagement>
  </build>

specific language governing permissions and limitations
under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>
  <artifactId>foo</artifactId>
  <groupId>foo</groupId>
  <version>99.44</version>
  <packaging>bleh</packaging>
  <dependencies>
    <dependency>
      <artifactId>artifactId</artifactId>
      <groupId>groupId</groupId>
    </dependency>
  </dependencies>

specific language governing permissions and limitations
under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>
  <artifactId>foo</artifactId>
  <groupId>foo</groupId>
  <version>99.44</version>
  <packaging>bleh</packaging>
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-it-plugin</artifactId>
      </plugin>
    </plugins>
  </build>

specific language governing permissions and limitations
under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>
  <artifactId>foo</artifactId>
  <groupId>foo</groupId>
  <version>99.44</version>
  <packaging>bleh</packaging>
  <dependencyManagement>
    <dependencies>
      <dependency>
        <artifactId>artifactId</artifactId>
        <groupId>groupId</groupId>
      </dependency>

Guillaume Nodet <******@****.***> 1729859506 +0200

        or other situation, under Python's version specification rules,
        `tensorflow[and-cuda]==2.15.0` will not install this fixed version.
        Please use `==2.15.0.post1` to specify this exact version on Linux
        platforms, or a fuzzy version specification, such as `==2.15.*`, to
        specify the most recent compatible version of TensorFlow 2.15 on all
        platforms.

# Release 2.15.0

Guillaume Nodet <******@****.***> 1729859506 +0200

Guillaume Nodet <******@****.***> 1729859506 +0200

<!-- If Yes, optionally please include minio version or commit id or PR# that caused this regression, if you have these details. -->

## Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->
* Version used (`minio --version`):
* Server setup and configuration:

   * com.google.common.testing.junit4.TearDownTestCase} for example.
   *
   * <p>A failing {@link TearDown} may or may not fail a tl4j test, depending on the version of
   * JUnit test case you are running under. To avoid failing in the face of an exception regardless
   * of JUnit version, implement a {@link SloppyTearDown} instead.
   *
   * <p>tl4j details: For backwards compatibility, {@code junit3.TearDownTestCase} currently does