[
https://issues.apache.org/jira/browse/LUCENE-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987536#action_12987536
]
Uwe Schindler commented on LUCENE-2609:
---------------------------------------
{quote}
bq. If it will make things any simpler, then let's put all the framework
classes under src/test/o.a.l/framework and have simple target which jars up
everything underneath it.
Well i mean sounds good (so do parts of Uwe's idea too).
But, some of this stuff is in packages for a reason, it uses package-private
hacks to improve test-coverage, etc.
So if we do this, we need to expose lots of things as 'public' and
@lucene.internal for testing, possibly even whole
classes (haven't looked in a while).
{quote}
This is different in my proposal. The copy task from shais task would be done
one time to a different and self-contained src/test-base (need better name).
That gets compiled separate and produces jar file.
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.
> 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
