You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@harmony.apache.org by Mark Hindess <ma...@googlemail.com> on 2009/03/24 13:46:48 UTC

[modularity] swing specific test base classes in common support jar?

Anyone know why the javax.swing.*TestCase and
javax.swing.text.parser.utils.DTDGetter classes are in the common test
support jar?  I think they should be maintained in modules/swing since they
are specific to that module.

Regards,
 Mark.

Re: [modularity] swing specific test base classes in common support jar?

Posted by Nathan Beyer <nd...@apache.org>.

Yeah, that's always seemed a bit of sore. Makes sense to clean it up
if you can - go for it.

-Nathan

On Tue, Mar 24, 2009 at 8:48 AM, Tim Ellison <t....@gmail.com> wrote:
> Mark Hindess wrote:
>> Anyone know why the javax.swing.*TestCase and
>> javax.swing.text.parser.utils.DTDGetter classes are in the common test
>> support jar?  I think they should be maintained in modules/swing since they
>> are specific to that module.
>
> I agree that they should be moved into the Swing module.  Indeed, I have
> a patch sitting in my queue that goes some way to achieving that.  Once
> we exit code freeze I can apply it, or share it to let you see where it
> was going.
>
> Regards,
> Tim
>

Re: [modularity] swing specific test base classes in common support jar?

Posted by Tim Ellison <t....@gmail.com>.

Mark Hindess wrote:
> Anyone know why the javax.swing.*TestCase and
> javax.swing.text.parser.utils.DTDGetter classes are in the common test
> support jar?  I think they should be maintained in modules/swing since they
> are specific to that module.

I agree that they should be moved into the Swing module.  Indeed, I have
a patch sitting in my queue that goes some way to achieving that.  Once
we exit code freeze I can apply it, or share it to let you see where it
was going.

Regards,
Tim