Re: [Junit-devel] Using APT as preprocessor for Junit annotations (Patch - 1581916)

[David S. <sa...@mi...>]

On 11/3/06, Jun...@li... <
Jun...@li...> wrote:

> This is certainly true for smaller projects and test suits. Might be
> nice though, to find some of the problems *before* proceding into an
> half hour build and test cycle, if you are just using ANT.



I can understand that.


> One reason for a little inertia here is that Kent and Erich have tried
> > to maintain a position as a "leaf in the technology tree", that is,
> > having dependency on nothing but Java.
>
> Nothing to add there. Sure enough, the patch currently doesn't add any
> other dependency outside of the JDK 1.5 tools.jar.



tools.jar already contains APT?  I wasn't aware of that (as I said, I'm new
here.  :-)


- While writing the processor, some of the design choices for junit
> annotations proved critical. This is especially the case, if the
> presence of certain annotations at one declaration is in subtle ways
> depending on the presence/absence of others.
> E. g.: what should be the behavior of junit for class having
> @RunWith(Suite.class), no @Suite.Classes() but a @Parameters method?
> What about having several methods annotated with @Parameters in the same
> hierarchie of classes?



You had mentioned earlier the idea that there are several runners that are
somewhat redundant with their "characteristic" further-information
annotations.  I think that this can lead to some interesting new design
choices, but I'm still ruminating about that.

For now, the next thing for me to do is probably look at the code and run
it, and that will help us think further.  I can't promise I'll get to it in
less than a week.  Thanks,

   David Saff