About the nature of org.eclipse.m2e.core.maven2Nature issue

[GoogleCodeExporter]

I fixed this method of ProjectUtil.isMavenProject() to check with the new maven 
nature issue.

Please take a look at the attached patch file.

Original issue reported on code.google.com by jumperc...@gmail.com on 10 Nov 2014 at 8:09

Attachments:

• patch.txt

[GoogleCodeExporter]

Ohh, what issue does this fix? and is there a snapshot build with this change 
instead of me building the plugin please :(

Original comment by krishna81m on 19 Nov 2014 at 3:52

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

[GoogleCodeExporter]

Without this fixed, RJR will add some wrong classpath into the current project, 
if there contain multi-maven projects.
For example,
A depends on B (test scope or provided scope)
B depends on C
A contains (ZK 7.0.0), B contains (ZK 6.5.0), and C contains (ZK 5.0.0)
RJR will add these jars, ZK 5.0.0, 6.5.0, and 7.0.0, into the A runtime 
classpath.

The attached file fixed this issue and #188 issue.

Original comment by jumperc...@gmail.com on 19 Nov 2014 at 6:08

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

Attachments:

• 1.3.3-11.17.2014.zip