[
https://issues.apache.org/jira/browse/LUCENE-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987552#action_12987552
]
Shai Erera commented on LUCENE-2609:
------------------------------------
To summarize the plan then:
* We'll separate tests into src/test and src/test-base (you're welcome to
suggest better name)
** Under test-base we put the framework classes
** Under test we put the actual test cases (and all other classes that are not
'framework'?)
* Keep package names the same under each
* jar-test-core will jar up test-base
In a follow on issue, we fix the build to depend on test-base when compiling
tests. We can also make the same changes to Solr tests and let Solr's test-base
depend on Lucene's test-base and Solr's test depend on Solr's test-base. Maybe
this is an issue to open under Solr's JIRA as a follow on?
> Generate jar containing test classes.
> -------------------------------------
>
> Key: LUCENE-2609
> URL: https://issues.apache.org/jira/browse/LUCENE-2609
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Build
> Affects Versions: 3.0.2
> Reporter: Drew Farris
> Assignee: Shai Erera
> Priority: Minor
> Fix For: 3.1, 4.0
>
> Attachments: LUCENE-2609.patch, LUCENE-2609.patch, LUCENE-2609.patch
>
>
> The test classes are useful for writing unit tests for code external to the
> Lucene project. It would be helpful to build a jar of these classes and
> publish them as a maven dependency.
--
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]
