Hi,
I think this opens up a bigger issue, and the kick off for 3.6 will be
the time, as API changes (if not entirely new plugins) will be needed.
There has been some cleaning up done to make JUnit4 a little better
supported, but the sense I got is that there is frustration around
JUnit being a moving target.
Teasing the functionality out of JDT would be a great contribution, I
think, especially having multiple "adopters" evolving the API.
On 02/06/2009 16:22, Oisin Hurley wrote:
Personally, I don't think it would matter much if it is your or I who files
the bugzilla. The fact that a request comes from the community of users
instead of the project team can sometimes be advantageous and I will of
course back you up. If you offer to help, even better.
+1 from me - if possible, I'd like to help out in some small manner
with getting the junits sorted out.
--oh
_______________________________________________
buckminster-dev mailing list
buckminster-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/buckminster-dev
|
