I have a few projects that are setup and build with maven.

One of these (my serverframework) contains a test framework and some test packages that are used by the other projects. 
The test stuff is located in the src\test\java.. folder and is not included in the normal serverframework.jar, but in the serverframework-test.jar.

My other project has a normal dependency to the serverframework, as well as a dependency to the serverframework-test.jar as the testframework herein is used in this project as well.

<dependency>
  <groupId>xx</groupId>
  <artifactId>serverframework</artifactId>
  <version>${project.version}</version>
</dependency>
<dependency>
  <groupId>xx</groupId>
  <artifactId>serverframework</artifactId>
  <version>${project.version}</version>
  <type>test-jar</type>
  <scope>test</scope>
</dependency>

This work just fine when compiling and running tests on the projects that has dependencies to the serverframework.

The problem is that in the java editor all references in the refering project to the classes in the testframework in the serverframework is marked as errors.
This can be explained by the editor using the maven artifact from the first dependency. However, as this is a class in the test packages, i would suppose that the editor used the <scope>test</scope> artiface, which is containing the classes refered.

I think this issue has been introduced within the last couple of weeks (i see it now in 201210020001, and have also seen it in 201209260001 and 201209220001.
Before that i did not get these errors.