Versions Compared

Old Version 1

changes.mady.by.user Brett Porter

Saved on

compared with

New Version 2

changes.mady.by.user Brett Porter

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

With the advent of version ranges, this will require use to get a list of versions for an artifact also. This has gotten to "critical mass" of metadata that we should move to handling general directory metadata.

We can safely remove /rename reading of plugins.xml now since there hasn't been a release cut that uses it, and there are not significant amounts to convert in the repo. We should continue to read the others, but deprecate it.

Location of metadata

Metadata will be stored at the directory level, allowing different metadata for each granularity. The file will be called maven-metadata.xml

Version Information for Artifact Directories

Code Block
xml
xml

<metadata>
  <versioning>
    <release>1.0.2</release>
    <latest>1.0.3-SNAPSHOT</latest>
    <snapshot>1.0.3-20051011.123014-5</snapshot>
    <versions>
      <version>1.0.0-SNAPSHOT</version>
      <version>1.0.0</version>
      <version>1.0.1-SNAPSHOT</version>
      <version>1.0.1</version>
      <version>1.0.2-SNAPSHOT</version>
      <version>1.0.2</version>
      <version>1.0.3-SNAPSHOT</version>
    </versions>
  </versioning>
</metadata>
Note
titleVersion Ordering

The latest and even release metadata may not be needed if we are honoring a versionining scheme as determined from the POM - however, if that scheme changes over time the version order might not be consistent so it is worth keeping here.
It is also possible that the list be ordered and the last is used for latest (and the last non-snapshot for release).

Plugin Information for Group Directories

Code Block
xml
xml

<metadata>
  <groupId>org.codehaus.mojo</groupId>
  <plugins>
    <plugin>
      <prefix>myPlugin</prefix>
      <artifactId>myPlugin-maven-plugin</artifactId>
    </plugin>
  </plugins>
</metadata>