A simple test case confirms it to be a JUnit issue. Perhaps since the
test runner itself is not package-local it can no longer access the
public methods in AbstractTestVector.
I changed the pom to use the latest Junit 4.8.2 and dropped the public
qualifier on AbstractTestVector. The tests all run again but I had to
manually install the JUnit jar since none of our repositories evidently
contain it.
On 5/23/10 1:11 PM, Sean Owen wrote:
I doubt it is to do with Java itself since I did not see this behavior. This
shouldn't be a security issue.
I rather suspect a JUnit version issue somehow?
