/**
 * Tests {@link ArtifactUtils}.
 *
 */
class ArtifactUtilsTest {

    private Artifact newArtifact(String aid) {
        return new DefaultArtifact("group", aid, VersionRange.createFromVersion("1.0"), "test", "jar", "tests", null);
    }

    @Test
    void testIsSnapshot() {
        assertFalse(ArtifactUtils.isSnapshot(null));
        assertFalse(ArtifactUtils.isSnapshot(""));

        @SuppressWarnings("deprecation")
        List<Artifact> artifacts = project.getCompileArtifacts();
        assertEquals(1, artifacts.size());
        assertTrue(artifacts.get(0).getFile().getName().endsWith("tools.jar"));
    }

## OpenAPI condicional desde configuraciones y variables de entorno { #conditional-openapi-from-settings-and-env-vars }

Puedes usar fácilmente las mismas configuraciones de Pydantic para configurar tu OpenAPI generado y las interfaces de usuario de la documentación.

Por ejemplo:

We have a lifecycle mapping for the packaging of *jar* below. You see that for this packaging we have a *default* lifecycle and a list of phases where each phase is a comma separated list of goals to run and they are in the form groupId:artifactId:version.

<configuration>
  <lifecycles>
    <lifecycle>
      <id>default</id>
      <phases>
        <process-resources>org.apache.maven.plugins:maven-resources-plugin:resources</process-resources>

		if !db.DryRun && db.Error == nil {
			if ok, mode := hasReturning(db, supportReturning); ok {
				if rows, err := db.Statement.ConnPool.QueryContext(db.Statement.Context, db.Statement.SQL.String(), db.Statement.Vars...); db.AddError(err) == nil {
					dest := db.Statement.Dest
					db.Statement.Dest = db.Statement.ReflectValue.Addr().Interface()
					gorm.Scan(rows, db, mode)
					db.Statement.Dest = dest
					db.AddError(rows.Close())

 * <p>
 * This interface allows plugins and extensions to define and register additional packaging types
 * beyond the standard ones provided by Maven (like jar, war, ear, etc.). Implementations of this
 * interface will be discovered through the Java ServiceLoader mechanism and their provided
 * packaging types will be available throughout the Maven build process.
 * <p>
 * Example usage:

						dbName = f.DBName
					}
				}

				if tx.Statement.Distinct {
					expr = clause.Expr{SQL: "COUNT(DISTINCT(?))", Vars: []interface{}{clause.Column{Name: dbName}}}
				} else if dbName != "*" {
					expr = clause.Expr{SQL: "COUNT(?)", Vars: []interface{}{clause.Column{Name: dbName}}}
				}
			}
		}

		tx.Statement.AddClause(clause.Select{Expression: expr})
	}

    </dependency>
    <dependency>
      <groupId>test</groupId>
      <artifactId>b</artifactId>
      <version>0.1</version>
      <scope>system</scope>
      <systemPath>${java.home}/lib/good.jar</systemPath>
    </dependency>
  </dependencies>

under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its</groupId>
  <artifactId>b</artifactId>
  <version>0.1</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: Dummy Artifact</name>
  <description>

  </description>

  <distributionManagement>
    <repository>
      <id>maven-core-it</id>

under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its</groupId>
  <artifactId>a</artifactId>
  <version>0.1</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: Dummy Artifact</name>
  <description>

  </description>

  <distributionManagement>
    <repository>
      <id>maven-core-it</id>