Good idea! I tried to do this already in the test itself. Didn't work and i did not look further .

Verstuurd vanaf mijn iPhone

> Op 3 jan. 2014 om 19:54 heeft Gunnar Morling <notifications@github.com> het volgende geschreven:
> 
> In processor/src/test/java/org/mapstruct/ap/test/conversion/generics/ConversionTest.java:
> 
> > +import static org.fest.assertions.Assertions.assertThat;
> > +import org.mapstruct.ap.testutil.compilation.annotation.CompilationResult;
> > +import org.mapstruct.ap.testutil.compilation.annotation.Diagnostic;
> > +import org.mapstruct.ap.testutil.compilation.annotation.ExpectedCompilationOutcome;
> > +
> > +public class ConversionTest extends MapperTestBase {
> > +
> > +    @Test
> > +    @WithClasses( { ErroneousSource1.class, ErroneousTarget1.class, ErroneousSource2.class, ErroneousTarget2.class,
> > +        ErroneousSource3.class, ErroneousTarget3.class,  ErroneousSource4.class, ErroneousTarget4.class,
> > +        ErroneousSource5.class, ErroneousTarget5.class,
> > +        GenericTypeMapper.class, Wrapper.class, ArrayWrapper.class, TwoArgHolder.class, TwoArgWrapper.class,
> > +        TypeA.class, TypeB.class, TypeC.class, UpperBoundWrapper.class, Source.class, Target.class,
> > +        WildCardExtendsWrapper.class, WildCardSuperWrapper.class, WildCardExtendsMBWrapper.class,
> > +        SourceTargetMapper.class } )
> > +    public void shouldApplyGenericTypeMapper() {
> Many thanks for the thorough tests!
> 
> Regarding the usage of @WithClasses, it seems as if many of the referenced types are the same for all/several test methods. I'm wondering whether we should merge the type lists given on the class and the method level. That way one could specify a basic list with classes used in all test methods on the class level and only add the specific types on the method level.
> 
> WDYT? That'd require a small fix in MapperTestBase#getTestClasses().
> 
> —
> Reply to this email directly or view it on GitHub.