lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3329) Maven artifact for lucene-test-framework is identical to lucene-core artifact
Date Wed, 20 Jul 2011 12:35:57 GMT


Steven Rowe commented on LUCENE-3329:

Here's the patch:

Index: lucene/build.xml
--- lucene/build.xml    (revision 1148712)
+++ lucene/build.xml    (working copy)
@@ -410,7 +410,8 @@
-      <m2-deploy pom.xml="src/test-framework/pom.xml">
+      <m2-deploy pom.xml="src/test-framework/pom.xml"
+                 jar.file="${build.dir}/lucene-test-framework-${version}.jar">
           <attach file="${build.dir}/lucene-test-framework-${version}-src.jar"

Committing shortly.

> Maven artifact for lucene-test-framework is identical to lucene-core artifact
> -----------------------------------------------------------------------------
>                 Key: LUCENE-3329
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: general/build
>    Affects Versions: 3.4, 4.0
>            Reporter: Steven Rowe
> 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 {{$\{\}.jar}}.  Since lucene-test-framework artifacts are built
by the base lucene module, {{$\{\}}} 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.

This message is automatically generated by JIRA.
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message