[ 
https://issues.apache.org/jira/browse/SOLR-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919793#action_12919793
 ] 

Robert Muir commented on SOLR-2002:
-----------------------------------

+1 to fixing this situation, from the ant perspective.

When a single build.xml is responsible for building multiple "targets", it 
creates a mess.

Instead, if every folder is its own standalone module, then we could have a 
much simpler
recursive build. Adding something new like findbugs integration would then be 
trivial, it could 
be added in one place and affect all of lucene/solr.

Some suggestions:
* I think common should be its own folder.
* I think we should move lucene/src/demo to lucene/contrib/demo in 3.x like we 
did in trunk.


> improve build/tests
> -------------------
>
>                 Key: SOLR-2002
>                 URL: https://issues.apache.org/jira/browse/SOLR-2002
>             Project: Solr
>          Issue Type: Task
>          Components: Build
>            Reporter: Robert Muir
>            Assignee: Robert Muir
>            Priority: Minor
>             Fix For: 3.1, 4.0
>
>         Attachments: SOLR-2002.patch, SOLR-2002_core_contrib.patch, 
> SOLR-2002_localization.patch, SOLR-2002_lucenetestcase.patch, 
> SOLR-2002_merged.patch, SOLR-2002_merged.patch, SOLR-2002_merged.patch, 
> SOLR-2002_merged.patch, SOLR-2002_replication.patch, 
> SOLR-2002_testiter.patch, SOLR-2002_testmethod.patch, 
> SOLR-2002_timeout.patch, SOLR-2002setupteardown.patch
>
>
> we are working on improving some functionality in lucene's build/tests, it 
> would be good to improve the solr side to take advantage of it.
> currently its only sorta-kinda integrated and a bit messy.
> i'd like to do some incremental improvements piece-by-piece on this issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Reply via email to