[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ajdt-dev] Organizing projects, in paths, aspect paths etc..
|
Hi Simone,
As Andrew mentions, the latest AJDT 1.5.3 rc includes a lot of support
to make aspect path and in path
more work in a more eclipsey way. But answering your specific questions:
> I have to specify an inpath and aspectpath for each project. Many of
> them, depends on the same inpath and aspectpath. This causes a number of
> errors, expecially with inter type declarations, because the same aspect
> will be applied more than once to the same target, simply because there
> are more than one project having the same inpath and aspectpath.
Is there not a project configuration where you ensure the aspects
only weave what is in your project and you express dependencies on other
projects with classpath references rather than inpath references?
(Since classpath
referenced elements will not be woven). I guess I need to know a bit more about
how the interdependencies are causing you problems - can you describe a complete
example setup?
> Is there a way to tell
> AJDT to use inpath and aspectpath only to check code and not to acually
> weave classes?
no, you can't do that. If you want the code to be referenced but not woven then
use classpath. Files from aspectpath are never woven, it is just used to
discover aspects.
> Since inpath and aspectpath does not support projects,
> but class folders, will it behave in a better way if I package each
> project in a jar and use jars instead of class folders (apart from
> having to rebuild the jars every time :) )?
Maybe the 1.5.3 changes solve your problem, but please respond if they do not.
Andy.
