[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jdt-dev] Generalize JUnit view?
|
We can discuss it further on bug 507626 [1].
Regards,
Noopur
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=507626
Christian Pontesegger ---01/29/2019 01:14:10 AM---I was wondering what the best approach would be. Should we go for one Unit Test view which would be
From: Christian Pontesegger <christian.pontesegger@xxxxxx>
To: "Eclipse JDT general developers list." <jdt-dev@xxxxxxxxxxx>
Date: 01/29/2019 01:14 AM
Subject: Re: [jdt-dev] Generalize JUnit view?
Sent by: jdt-dev-bounces@xxxxxxxxxxx
I was wondering what the best approach would be. Should we go for one
Unit Test view which would be reused from all components? Or better
have a UnitTestComposite and some reusable command handlers which then
can be used for dedicated JUnit, C++Unit, ... views?
What would be the host project for these generalized components? Having
a dependency to JDT might not be first choice for other languages.
Probably platform.debug or platform.ui might be good choices.
Once we have an idea how to proceed I can offer to start with the
prototype. Basically copy the current state and carve it out from JDT.
Once it is stable other projects could then move to the new API.
Christian
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jdt-dev
