| Hi Mario,
Thanx for the very quick feedback!
You are right, I will fix the date ;-)
Using META-INF for aop.xml does not work, if you want to weave your aspects into other bundles. You have to put it somewhere on the bundle's classpath as well as export it. That did not change since I know Equinox Aspects ...
Of course you can use any exported package. The suggested best practice is to always use a certain one (org.aspectj or any other one), because you have to configure Equinox Aspects by setting the system property org.aspectj.weaver.loadtime.configuration to each and every aop.xml path. Better to just use one, otherwise you will probably miss one ...
Regards Heiko Am 13.06.2008 um 09:48 schrieb Mario Scalas: Just a notice: the message in the start page says:
"Mar 10 - ![]() We reworked this website an [...]"
I guess it is more recent than that :)
Another thing: in the quick-start guide it is written:
Put your aop.xml file into an exported package, if you want to weave other bundles. Best practice: Always use org.aspectj as package name, as this name also has to be provided as a system property for runtime (later).
All the examples I've seen did put this aop.xml into META-INF/ directory: I guess that the org.aspectj is the official way to go now, even if the property can be changed at will.
Regards
Mario
--
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan _______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
|
