I've wrote a plugin using AJDT, when I run my source as Eclipse Application, the aspects works.
But when I exports the source as a plugin and move the plugin.jar to my Eclipse_Root/plugins directory, the plugin runs wield.
- source of UI part runs well, extension point(org.eclipse.ui.menus) part shows in UI
- source of Aspects part does't work, as my log in around method doesn't log anything.
My config.ini was set like below:
I just follow the wiki and [run as Eclipse Application] works well, so I think the MF is not the problem.
How could I confirm the aspects getting compiled?
The AJDT uses the Equinox weaving and modify the class file before target plugin is activated(? I think) Before the Eclipse starting, the class file should be modified by aspects?
You need to open up the jar files and make sure that all of your .aj files have been compiled into .class files. Also, you need to make sure that the org.aspectj bundle is in your osgi manifest. Equinox weaving will weave your aspects into the java files when the java files are loaded.
> Equinox weaving will weave your aspects into the java files when the java files are loaded.
Maybe I have some misunderstandings. As your sayings, first weave .java file, then do ajbuild into .class, is that means I should have all the source bundles in my eclipse?