Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 314049 - compiler errors in two jsf bundles
Summary: compiler errors in two jsf bundles
Status: RESOLVED WORKSFORME
Alias: None
Product: Java Server Faces
Classification: WebTools
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 3.2 RC4   Edit
Assignee: Cameron Bateman CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-23 14:22 EDT by David Williams CLA
Modified: 2010-05-28 19:15 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2010-05-23 14:22:56 EDT 
After recently moving up to another ide dev. env, I started getting many (hundreds) of "problem markers" due to two jsf test bundles. Missing imports, something about the @Test annotation. 

org.eclipse.jst.jsf.core.tests
org.eclipse.jst.jsf.test.util

I'm not sure why these didn't show up before, or if there are other, better fixes, but it appears the bundles _require_ JUnit 4.x. If I change the manifest.mf to prereq org.junit 4.5 (instead of 3.8) then the problem markers go away. Not sure if there's other solutions, or not. 

If they do really require junit 4.x, then the manifest.mf should accurately reflect that.
Comment 1 Cameron Bateman CLA 2010-05-25 02:35:23 EDT 
The last time I tried to rev the lower bound on the JUnit requirement above 3.8 it broke the build.  I will revisit.
Comment 2 Cameron Bateman CLA 2010-05-25 18:42:58 EDT 
I can't repro this locally and the build server seems ok.  Can you still reproduce?
Comment 3 David Williams CLA 2010-05-28 19:15:44 EDT 
No, I don't see any longer. After "setting back" the prereq version by using "replace with ... " latest from head. 

So, not sure what the issue was/is. 

Thanks,