Sure, yes we'd like to keep JUnit tests running in order to always know their status, but currently it seems like site is not produced because of thise failures.

/Victor

On 03/18/2016 11:58 AM, Mickael Istria wrote:
On 03/18/2016 09:51 AM, Victor V. Rubezhny wrote:
I'd suggest to disable JUnit tests until they are fixed.
I'd suggest the contrary since disabled tests tend to be forgotten and never be re-enabled, and Making sure there is no regression and keeping test green is actually a very important part of such a refactoring, those tests should remain failing in a visible way until things work.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets <http://twitter.com/mickaelistria>


_______________________________________________
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev


--


CONFIDENTIALITY NOTICE: This email and files attached to it are confidential. If you are not the intended recipient you are hereby notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email.
_______________________________________________
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Reply via email to