[
https://issues.apache.org/jira/browse/LUCENE-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987540#action_12987540
]
Robert Muir commented on LUCENE-2609:
-------------------------------------
bq. The real tests are compiled later and not jared and reference the jar or
build/classes/test-base in classpath. Then packages are identical and no
problems occur.
This is much better, because it resolves some practical concerns.
* the package namespace is unchanged, we can still use pkg-private stuff
* there is no hardcoded list, we can still eclipse-refactor and run 'ant test'
and the build will not break. So, its
still easy to refactor tests.
It would require some up-front work to the build etc, but could be good, for
example to simplify up2date macros
where moduleA's tests depend upon base classes of moduleB (this is currently
messy).
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
