[
https://issues.apache.org/jira/browse/LABS-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762484#action_12762484
]
Simone Gianni commented on LABS-410:
------------------------------------
Thanks to recent fixes in AJDT it's now possible to add stuff to both inpath
and aspectpath.
The trick is to add the entire maven container to both paths, and the restrict
it using names of dependencies we want included (in our case, dependency
projects).
This works from a binary POV. AJDT does not take into account that it also has
the source code for those projects to build its model, so the model is limited,
giving a suboptimal editor feedback.
As it is now, having an aspect in the main project weaving a dependency class
is correctly reported (cause the source is considered), while having an aspect
in a dependency weaving a class in the main project is not correctly reported
(cause the source is NOT considered).
This is however the best solution actually available, cause it still compiles
properly (also when running junit tests), does not give any Eclipse sideffects,
and leaves to Eclipse and AJDT the task of properly coordinating and optimizing
the build cycle between interdependant projects, thus reducing cpu cycles and
memory consumption.
> [eclipse] Linked source folder for project which are a dependency
> -----------------------------------------------------------------
>
> Key: LABS-410
> URL: https://issues.apache.org/jira/browse/LABS-410
> Project: Labs
> Issue Type: Improvement
> Components: Magma
> Affects Versions: Next
> Reporter: Simone Gianni
> Fix For: Next
>
>
> The Magma Eclipse plugin currently creates linked source folders for sources
> of Magma dependencies. This gives AJDT the ability to properly resolve all
> Magma aspects, ITDs, and also to weave in user's own aspects.
> When a project in the workspace is added as a dependency, however, only the
> binary output folder of the project is exposed to AJDT, giving access only to
> stuff already weaved there, but not using aspects in that project or giving
> the ability to weave into it.
> AJDT only offers ways to add the project to the inpath or to the aspectpath,
> as opposed to a LTW-like environment.
> So, we need linked sources also for those projects.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
