Lucene - Core
  1. Lucene - Core
  2. LUCENE-3543

Add previous versions to maven-metadata.xml files generated by 'ant generate-maven-artifacts'

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 3.4, 4.0-ALPHA
    • Fix Version/s: None
    • Component/s: general/build
    • Labels:
      None

      Description

      The generate-maven-artifacts target generates one maven-metadata.xml file per artifact. In a repository, these files should contain a list of all previous releases along with the current release, but because Maven Ant Tasks doesn't have access to these versions, it does not include them in the files it produces.

      Two possible solutions:

      1. download Maven central's versions of the files prior to running generate-maven-artifacts and pre-populate the target local repository; or
      2. post-process the files to include the previous versions - this would require some form of access to the previously released versions for each artifact being published

        Activity

        Hide
        Steve Rowe added a comment -

        Maven artifacts are no longer pushed to repositories from the internal-repository-structure-on-a-local-filesystem created by ant generate-maven-artifacts. Instead:

        • snapshot artifacts are uploaded to the ASF snapshot repository by Jenkins nightly jobs via ant generate-maven-artifacts with properties m2.repository.id and m2.repository.url defined such that the artifacts go over the wire instead of being hosted by Jenkins; and
        • release artifacts are staged to the ASF release repository via ant stage-maven-artifacts: LUCENE-3964.
        Show
        Steve Rowe added a comment - Maven artifacts are no longer pushed to repositories from the internal-repository-structure-on-a-local-filesystem created by ant generate-maven-artifacts . Instead: snapshot artifacts are uploaded to the ASF snapshot repository by Jenkins nightly jobs via ant generate-maven-artifacts with properties m2.repository.id and m2.repository.url defined such that the artifacts go over the wire instead of being hosted by Jenkins; and release artifacts are staged to the ASF release repository via ant stage-maven-artifacts : LUCENE-3964 .

          People

          • Assignee:
            Steve Rowe
            Reporter:
            Steve Rowe
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development