Re: [platform-releng-dev] Changes to accommodate using JUnit4 in the Ecl

[David M Williams <david_williams@xxxxxxxxxx>]

I'm wondering how this effects projects like us in WTP that use your test 
framework. In particular, when you say you are making this change on 
Thursday ... is that for your "final" I-build for this week? Or is it more 
like the first run of an I-build for next week? 
Just trying to decide when "we" would see these changes ... and thus when 
"we" might have to react? 

Thanks, 





From:
Kim Moir <Kim_Moir@xxxxxxxxxx>
To:
platform-releng-dev@xxxxxxxxxxx
Date:
11/16/2009 04:58 PM
Subject:
[platform-releng-dev] Changes to accomodate using JUnit4 in the Eclipse 
Test framework
Sent by:
platform-releng-dev-bounces@xxxxxxxxxxx




DJ and I have been testing changes to the Eclipse Test Framework so our 
tests can run on Junit 4 instead of Junit 3.  Last week we had a 
successful build from our test branch where all tests passed.   

On Thursday November 19, I'd like to merge the changes into HEAD and and 
run a full test build. Most of the changes are to the manifests of the 
test bundles to specify a only lower bound for org.junit for version 
3.8.2.  There are a few code changes as well, which have been tested. 
Below is a list of the bundles that require changes, as well a link to a 
bug with a patch that encompasses all these changes.   

I'd like to ask the teams to review the changes that apply to their 
bundles and update the bug if you see any issues.  I'd like to start the 
test build at 8am on Thursday.  If you would like to release the changes 
after 1am but  before 8am EST on Thursday, that would be great, otherwise 
I would be happy to release them for you.    Please don't release any 
changes before Thursday morning because the build will fail. 

Bundles requiring changes 

org.eclipse.core.expressions.tests 
org.eclipse.pde.build.tests 
org.eclipse.core.tests.harness 
feature@xxxxxxxxxxxxxxx feature 
org.eclipse.jdt.core.tests.builder 
org.eclipse.jdt.core.tests.compiler 
org.eclipse.jdt.core.tests.model 
org.eclipse.jdt.core.tests.performance 
org.eclipse.search.tests 
org.eclipse.ltk.core.refactoring.tests 
org.eclipse.ltk.ui.refactoring.tests 
org.eclipse.jdt.ui.tests 
org.eclipse.jdt.ui.tests.refactoring 
org.eclipse.jdt.junit.core 
org.eclipse.jdt.junit.runtime 
org.eclipse.jdt.junit4.runtime 
org.eclipse.equinox.frameworkadmin.test 
org.eclipse.equinox.p2.tests 
org.eclipse.equinox.p2.tests.ui 
org.eclipse.pde.junit.runtime 
org.eclipse.pde.ui.tests 
org.eclipse.team.tests.cvs.core 
org.eclipse.text.tests 
org.eclipse.jface.text.tests 
org.eclipse.core.filebuffers.tests 
org.eclipse.ui.workbench.texteditor.tests 
org.eclipse.ui.editors.tests 
org.eclipse.jdt.text.tests 

There are also changes to the org.junit4 bundle and the addition of a new 
bundle with a symbolic name of  org.junit and version of 4.5.0.qualifier. 

JUnit4 in Eclipse Testing Framework 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=153429 

Patch 
https://bugs.eclipse.org/bugs/attachment.cgi?id=152344 

If you have any questions, please let me know. 

thanks 
Kim_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev