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

Maven artifact for lucene-test-framework is identical to lucene-core artifact

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.4, 4.0-ALPHA
    • 3.4, 4.0-ALPHA
    • general/build
    • None
    • New, Patch Available

    Description

      No released version of the lucene-test-framework jar is affected.

      This bug was introduced by SOLR-2452. In the m2-deploy macro in lucene/common-build.xml, the names of jar files to deploy were previously drawn from the supplied POM, but since Solr's non-Maven jars don't follow the Maven naming scheme (apache- is prepended), the jar file name now defaults to ${final.name}.jar. Since lucene-test-framework artifacts are built by the base lucene module, ${final.name} is lucene-core-${version}, so when ant generate-maven-artifacts goes to copy the lucene-test-framework binary jar, it grabs the lucene-core binary jar instead.

      Attachments

        Activity

          People

            sarowe Steven Rowe
            sarowe Steven Rowe
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment