[
https://issues.apache.org/jira/browse/SOLR-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042428#comment-13042428
]
Steven Rowe commented on SOLR-2452:
-----------------------------------
Robert, I'm merging trunk to the SOLR-2452 branch, and I noticed that SOLR-2279
introduced a solr.directoryFactory <sysproperty> element in the <junit> task
invocation for all the Solr contribs.
I'm trying to figure out how to support this in the consolidated build without
duplicating code. My current thinking is to introduce an optional <element> in
the "test-macro" definition to supply the <sysproperty> to the <junit> task,
and then make new <junit-sequential-solr> and <junit-parallel-solr> targets,
including the solr.directoryFactory <sysprop> element in each <test-macro>
invocation. Then a new common-solr.test target would depend on the
junit-*-solr targets.
Thoughts?
> rewrite solr build system
> -------------------------
>
> Key: SOLR-2452
> URL: https://issues.apache.org/jira/browse/SOLR-2452
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 3.2, 4.0
>
>
> As discussed some in SOLR-2002 (but that issue is long and hard to follow), I
> think we should rewrite the solr build system.
> Its slow, cumbersome, and messy, and makes it hard for us to improve things.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
