[jira] [Created] (LUCENE-3329) Maven artifact for lucene-test-framework is identical to lucene-core artifact

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (LUCENE-3329) Maven artifact for lucene-test-framework is identical to lucene-core artifact

Nick Burch (Jira)
Maven artifact for lucene-test-framework is identical to lucene-core artifact
-----------------------------------------------------------------------------

                 Key: LUCENE-3329
                 URL: https://issues.apache.org/jira/browse/LUCENE-3329
             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 {{$\{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.



--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (LUCENE-3329) Maven artifact for lucene-test-framework is identical to lucene-core artifact

Nick Burch (Jira)

    [ https://issues.apache.org/jira/browse/LUCENE-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068328#comment-13068328 ]

Steven Rowe commented on LUCENE-3329:
-------------------------------------

Here's the patch:

{code:java}
Index: lucene/build.xml
===================================================================
--- lucene/build.xml    (revision 1148712)
+++ lucene/build.xml    (working copy)
@@ -410,7 +410,8 @@
                   classifier="javadoc"/>
         </artifact-attachments>
       </m2-deploy>
-      <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">
         <artifact-attachments>
           <attach file="${build.dir}/lucene-test-framework-${version}-src.jar"
                   classifier="sources"/>
{code}

Committing shortly.

> Maven artifact for lucene-test-framework is identical to lucene-core artifact
> -----------------------------------------------------------------------------
>
>                 Key: LUCENE-3329
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3329
>             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 {{$\{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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] [Resolved] (LUCENE-3329) Maven artifact for lucene-test-framework is identical to lucene-core artifact

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

     [ https://issues.apache.org/jira/browse/LUCENE-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Rowe resolved LUCENE-3329.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 4.0
                   3.4
         Assignee: Steven Rowe

Committed:
- r1148728: trunk
- r1148731: branch_3x

> Maven artifact for lucene-test-framework is identical to lucene-core artifact
> -----------------------------------------------------------------------------
>
>                 Key: LUCENE-3329
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3329
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: general/build
>    Affects Versions: 3.4, 4.0
>            Reporter: Steven Rowe
>            Assignee: Steven Rowe
>             Fix For: 3.4, 4.0
>
>
> 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]