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

Steven Rowe commented on LUCENE-4365:
-------------------------------------

Before applying the patch, run the following script:

{code}
svn --parents cp dev-tools/maven/lucene/core/pom.xml.template 
dev-tools/maven/lucene/core/src/java/
svn --parents cp dev-tools/maven/lucene/codecs/pom.xml.template 
dev-tools/maven/lucene/codecs/src/java/
svn --parents cp dev-tools/maven/solr/core/pom.xml.template 
dev-tools/maven/solr/core/src/java/
svn --parents cp dev-tools/maven/solr/solrj/pom.xml.template 
dev-tools/maven/solr/solrj/src/java/
{code}
                
> The Maven build can't directly handle complex inter-module dependencies 
> involving the test-framework modules
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-4365
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4365
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: general/build
>            Reporter: Steven Rowe
>            Assignee: Steven Rowe
>            Priority: Minor
>         Attachments: LUCENE-4365.patch, lucene.solr.dependency.cycles.png.jpg
>
>
> The Maven dependency model disallows cyclic dependencies, of which there are 
> now several in the Ant build (considering test and compile dependencies 
> together, as Maven does).  All of these cycles involve either the Lucene 
> test-framework or the Solr test-framework.
> The current Maven build works around this problem by incorporating 
> dependencies' sources into dependent modules' test sources, rather than 
> literally declaring the problematic dependencies as such. (See SOLR-3780 for 
> a recent example of putting this workaround in place for the Solrj module.)  
> But with the factoring out of the Lucene Codecs module, upon which Lucene 
> test-framework has a compile-time dependency, the complexity of the 
> workarounds required to make it all hang together is great enough that I want 
> to attempt a (Maven-build-only) module refactoring.  It should require fewer 
> contortions and be more maintainable.
> The Maven build is currently broken, as of the addition of the Codecs module 
> (LUCENE-4340).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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