Community
Participate
Working Groups
We have a multi-modules Maven project, one of the modules being a multi-modules project itself and made of jars containing Aspects. MAIN (pom) |- MODULE1 (jar) |- MODULE2 (jar) |- MODULE3 (war) |- ASPECT_MODULE (pom) |-- ASPECT_MOD1 (jar) |-- ASPECT_MOD2 (jar) |-- ASPECT_ALLMOD (über jar containing all the other aspect JARs) In the MAIN project, the JAR modules depends on the final JAR (ASPECT_ALLMOD) containing the aspects and these aspects have to be applied. This is achieved thru the <aspectLibraries> of the maven-aspectj-plugin, and it's works perfectly when building the project under Maven. However, when building the project under Eclipse (STS version based on Luna in our case), IF the sub-projects containing the Aspects (ASPECT_MODULE and its descendants) are opened in the workspace, then the Aspects are not applied and this is directly visible by the fact that the AspectJ markers disappear when looking at source code of any of the MODULE_x's class. When looking at the AspectJ build under the Project->Properties, in the tab "Aspect Path", the referenced Aspect JAR (ASPECT_ALLMOD) is displayed with the icon of a folder when its project is opened in the workspace. As soon as we close the project, the icon turn into a JAR one and everything works as expected. It looks like the fact that the project's reference change of "nature" influences the behaviour of the AspectJ integration in Eclipse.
I think this is the maven tooling trying to be helpful. Can you check the project settings and see if this changes the behavior? For the dependent projects, open Project Properties, select 'maven' on the left - it should show the option "resolve dependencies from workspace projects" can you deselect that?
