Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-5420

'ant get-maven-poms' should support custom version formats

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: general/build
    • Labels:
      None
    • Lucene Fields:
      New, Patch Available

      Description

      LUCENE-5217 changed the way ant get-maven-poms works, so that dependencies are pulled from the Ant build, instead of being hard-coded in the POM templates. To parse the versions from internal module dependencies, the new internal Ant task GetMavenDependenciesTask uses a regex that expects a dotted/slashed/underscored numeric + optional -SNAPSHOT version format. As a result, non-conforming versions trigger a build failure - see the lucene-dev mailing list thread "maven build issues with non-numeric custom version": <http://mail-archives.apache.org/mod_mbox/lucene-dev/201401.mbox/%3cCAF=Pa5-0sXE9Su1PgF5M+F0T+g3Q=fetWgXDh5Ry1ab3ZRhquQ@mail.gmail.com%3e>

      This is a regression, since previously, custom version strings worked properly, e.g. ant -Dversion=my-custom-version get-maven-poms.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: