> Hummm... I don't have to turn a project into a Maven project, if there
> is a pom.xml I can do Maven things with it. Why can't I just have a
> project with a build.gradle and do Gradle things with it?
Actually, that's not correct. There are two ways to import maven projects:
1. by first calling mvn eclipse:eclipse
2. by importing through the m2eclipse plugin
The first way will turn it into a vanilla eclipse project with no
special maven support, and the second has maven support baked into it.
If you import through #1 and you want maven support, then you have to
explicitly enable it (you may need to even delete it and then delete
the eclipse project files, and then reimport it).
With grade, you can use the eclipse plugin for gradle to mimic #1.
Or, you can mimic #2 through the new tooling for Gradle in Eclipse.
However, if you initially import through #1, then you need to
explicitly enable the tooling. So, in this sense, the gradle tooling
follows the same paradigm as the maven tooling.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
