Some Symphony bundles with wrong Classpath definitions.
Issue #33
resolved
It is possible that wrong compiler settings (preferences) may raise errors and warnings related to incompatible JRE version. To reproduce the problem, install a fresh eclipse and follow the Symphony installation guide. Then see the errors in the Problems view. Update Class Path may be required on faulty Manifests.
Comments (2)
-
-
- changed status to resolved
- Log in to comment
Fixed as part of Issue
#41; this had to do with the fact that the project settings themselves referred to a different VM; this was quickly discovered when I was updating everything to 1.8. Simply by updating the classpath to use the right JRE fixed this problem and all relevant warning disappeared.