There are two kinds of error you can see with AJDT:
- the temporary errors that appear only in the editor and have no entry in the problems view
- permanent errors that appear in the editor and in the problems view
The former kind of error appears if you have JDT weaving turned off (see the project preferences). If they still exist with that on, it is a bug we need to fix.
The second kind of error can happen for two reasons: when the maven stuff fails to recognize that there are aspect libraries it should be using; or when the Javabuilder is being used instead of (or in addition to!) the ajbuilder.
When you say imported as via "Git import (general project)" - can you tell me exactly which menu options you are using? I have tried two routes:
1) Simply cloning (command line) then importing an 'existing maven project' - that works reliably for me.
2) Cloning then 'import existing project' (non maven). Because of the project structure this immediately turned on maven dependency management for me, and the project works.
I didn't run mvn eclipse:eclipse in either case.
In both cases I've played around with the project for a few minutes and am unable to cause any errors to appear.
I'm not denying there are errors, I just need a reliable way to make them appear so we can fix them. All the errors in your SDGErrors.txt file are what would appear if the project forgot there was an aspect library (or, even worse, had forgotten to build with AspectJ and dropped back to using the Java builder).
Indeed, if the AspectJ builder isn't being used (the java builder is being used instead), the aspects wont be in operation, leading to all these issues. I don't particularly trust the .project/.classpath that come with the myrestaurant-social project as the ajbuilder is mentioned twice in the default variant. Rebuilding them from scratch (deleting them then running mvn eclipse:eclipse) still produces double entries for ajbuilder which suggests to me that the pom isn't correct.
But fundamentally, we need a reliable set of steps to produce a broken project, I'm getting a bit confused about the various import/build options here. Can we distill it down to a consistent set of simple steps that show a broken project in eclipse? If using any eclipse maven support please include a version number.