[
https://issues.apache.org/jira/browse/LABS-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743844#action_12743844
]
Simone Gianni commented on LABS-410:
------------------------------------
This could bring another advantage, that is not requiring to clean install
dependencies separately when magma:run is invoked for a web project. In fact,
directing output of project linked source folders to a specific output folder,
and including it in the magma:run classpath, can ease the pain of rebuilding
them.
Since there could be exist a problem with duplicate resources however, this
solution has to be validated against generated magma.locals and possible
enhancements on that part before.
> [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: Current
> Reporter: Simone Gianni
> Fix For: Current
>
>
> 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]
