snapshot.setTimestamp(utcDateFormatter.format(timestamp));

            Versioning versioning = new Versioning();
            versioning.setSnapshot(snapshot);
            versioning.setLastUpdatedTimestamp(timestamp);
            lastUpdated = versioning.getLastUpdated();

            metadata.setVersioning(versioning);
        } else {
            snapshot = metadata.getVersioning().getSnapshot();

Die gebräuchlichste Methode besteht darin, eine Datei `requirements.txt` mit den Namen der Packages und deren Versionen zu erstellen, eine pro Zeile.

Sie würden natürlich die gleichen Ideen verwenden, die Sie in [Über FastAPI-Versionen](versions.md){.internal-link target=_blank} gelesen haben, um die Versionsbereiche festzulegen.

Ihre `requirements.txt` könnte beispielsweise so aussehen:

```

<?xml version="1.0" encoding="UTF-8"?><metadata>
  <groupId>org.apache.maven.its.mng3906</groupId>
  <artifactId>a</artifactId>
  <version>0.1</version>
  <versioning>
    <release>0.2</release>
    <versions>
      <version>0.1</version>
      <version>0.2</version>
    </versions>
    <lastUpdated>20081214111115</lastUpdated>
  </versioning>

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>org.apache.maven.its</groupId>
  <artifactId>b</artifactId>
  <version>0.1</version>
  <versioning>
    <versions>
      <version>0.1</version>
    </versions>
    <lastUpdated>20091023222817</lastUpdated>
  </versioning>

<?xml version="1.0" encoding="UTF-8"?><metadata>
  <groupId>org.apache.maven.its.mng3906</groupId>
  <artifactId>b</artifactId>
  <version>0.1</version>
  <versioning>
    <release>0.1</release>
    <versions>
      <version>0.1</version>
    </versions>
    <lastUpdated>20081214111129</lastUpdated>
  </versioning>

<?xml version="1.0" encoding="UTF-8"?><metadata>
  <groupId>org.apache.maven.its.mng3906</groupId>
  <artifactId>e</artifactId>
  <version>0.1</version>
  <versioning>
    <release>0.1</release>
    <versions>
      <version>0.1</version>
    </versions>
    <lastUpdated>20081214111155</lastUpdated>
  </versioning>

  It is more than simply understanding that m2 cannot go and check for the
  latest version of some snapshot artifact. If m2 is offline, SCM operations
  cannot succeed; no artifact downloads can take place, regardless of whether
  they are snapshot versions; artifact deployment cannot take place; certain
  types of tests cannot be setup, since the container used to run them cannot be

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-clean-plugin</artifactId>
  <version>0.1</version>
  <versioning>
    <latest>0.1</latest>
    <release>0.1</release>
    <versions>
      <version>0.1</version>
    </versions>
    <lastUpdated>20091023224342</lastUpdated>
  </versioning>

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-compiler-plugin</artifactId>
  <version>0.1</version>
  <versioning>
    <latest>0.1</latest>
    <release>0.1</release>
    <versions>
      <version>0.1</version>
    </versions>
    <lastUpdated>20091023224813</lastUpdated>
  </versioning>

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-deploy-plugin</artifactId>
  <version>0.1</version>
  <versioning>
    <latest>0.1</latest>
    <release>0.1</release>
    <versions>
      <version>0.1</version>
    </versions>
    <lastUpdated>20091023224421</lastUpdated>
  </versioning>