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

Steven Rowe updated LUCENE-3944:
--------------------------------

    Attachment: LUCENE-3944.patch

New trunk patch.

Robert pointed out on #lucene IRC that the Ant problem (Solr contrib ignoring 
an overridden {{dist-maven}} target definition in {{solr/common-build.xml}}) 
was as a result of the {{dist-maven}} specialization in 
{{solr/contrib/langid}}, which depended on the lucene definition instead of the 
overriding solr definition.  This is fixed in this version of the patch.

Also fixed in this version of the patch: a typo in the Solr definition of 
{{dist-maven}} that prevented it from finding the appropriate POM.

{{ant generate-maven-artifacts}} now works (succeeds anyway and puts the right 
stuff in the right place) under {{solr/}}, {{lucene/}}, and {{modules/}}.

I plan on doing more testing before committing, and then backporting to 
branch_3x.
                
> ant clean should remove pom.xml's
> ---------------------------------
>
>                 Key: LUCENE-3944
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3944
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: general/build
>            Reporter: Chris Male
>            Priority: Blocker
>             Fix For: 3.6, 4.0
>
>         Attachments: LUCENE-3944.patch, LUCENE-3944.patch
>
>
> Currently once the pom.xml's are in place, its hard to get them out.  Having 
> them can be a little trappy when you're trying to debug the bug.  We should 
> facilitate their removal during clean.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Reply via email to