Wrong source path lookup if RJR run with multi-maven projects

[GoogleCodeExporter]

If the multi-maven projects contain a same maven module with different version 
in 'test' or 'provided' maven scope, the default 
org.eclipse.jdt.launching.StandardSourcePathProvider will include all of the 
runtime classpath of the multi-maven projects to look up the source path.

I provided a patch to ignore the source path if the maven scope is 'test' or 
'provided'.

Original issue reported on code.google.com by jumperc...@gmail.com on 15 Nov 2014 at 1:08

Attachments:

• 0001-fix-RJR-to-pick-a-wrong-source-path-if-the-maven.sco.patch

[GoogleCodeExporter]

update the patch file

Original comment by jumperc...@gmail.com on 17 Nov 2014 at 4:37

• Added labels: ****
• Removed labels: ****

Attachments:

• 0001-fix-RJR-to-pick-a-wrong-source-path-if-the-maven.sco.patch