I think I do have a solution for this and will post a patch (will need to modify classpath.jelly) for this whenever I can.

• yujin

limitation: if the sub project is not under the current root, this probably won't work, ie if root project A and child project B are at the same level, instead of B residing under A, this will most likely fail.

also i didn't put too much effort into parsing the exclude filter for reactor. just checking if it's empty then add the root project. I think eventually the part that handles the single project and the code i added can be merged.

maven.multiproject.eclipse.includes: if not set, falls back to maven.multproject.includes, or "*/project.xml" if it's not set either
maven.multiproject.eclipse.excludes: to exclude subprojcet from being included in the eclipse classpath. (such as sandbox projects).

One issue I know still exists is when you have multiproject stucture for webapps. The way this is done, you can't have a subproject level dependency. Because eclipse doesn't support multi-tier project, for eclipse project to be able to see the dependencies is to have the dependencies declared at the top level project.

i'll submit a patch if/when the above patch(or the one in agila) makes it to the main tree.

1) Generated sources dir for nested projects should be obtained with something like this:

<j:set var="nestedContext" value="${reactorProject.context}"/>
<j:invoke var="genSrc" on="${nestedContext}" method="getVariable">
<j:arg value="maven.gen.src"/>
</j:invoke>

This way nested project's potentially different setting is respected. Same should be done for maven.build.dir

2) I put multiproject handling into a separate "multiclasspath.jelly" file and included it in the main classpath.jelly. I like smaller files as I feel they are easier to work with/find things in.