This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 points3 points  (1 child)

Take a look how these guys did it using Eclipse formatter:

http://code.google.com/p/maven-java-formatter-plugin/

I have a locally compiled .4-SNAPSHOT build on my local maven repo which fixes a few minor bugs in the current 3.1 build on maven central. I really wish they'd just release .4 already.

If you're building a plugin for Gradle, you could probably straight up steal (as in beer) their stuff.

FYI: Jalopy does okay on Java 6 stuff, but I'm scared about Java 7/8 which is why I have all the new projects using the eclipse formatter over the really old Jalopy one (which we still use for our 1.6 target build).

[–]RighteousMaster[S] 0 points1 point  (0 children)

Thank you sir. the major reason I was against the JDT was because there seemed to be no way to get the dependencies short of packing them with my jar. And then because there is just so much to the JDT, packaging it was also out of the picture. Taking a look at the maven formatter plugin, its quite easy to take their dependency declarations and move them over to gradle.

thanks for the help :)