On Thu, Jun 2, 2011 at 4:35 AM, Igor Drobiazko <[email protected]> wrote: > This is why Gradle rules. With Maven you depend on plenty of buggy, outdated > and undocumented plugins. If no plugin fits your need, you come up with your > own plugin. And it is a pain in the ass. With Gradle it's a matter of > writing a couple of lines of Groovy code. >
It's just like Tapestry ... you only need to write a couple of lines, but knowing which lines and where is a challenge. Their documentation is in many ways more detailed and complete, but it's also scattered, and much of the information you need to understand how builds work is actually not even in interfaces, but inside private implementations. > On Thu, Jun 2, 2011 at 12:34 AM, <[email protected]> wrote: >> >> + >> +/** Returns the tools.jar/classes.jar of the Java runtime. */ >> +File getTools() { >> + def relpath = isMacOSX() ? "../classes/classes.jar" : "../lib/tools.jar" >> + >> + return new File(System.properties['java.home'], relpath) >> +} >> + >> +boolean isMacOSX() { >> + System.properties['os.name'].toLowerCase().contains('mac os') >> +} >> + >> >> >> > > > -- > Best regards, > > Igor Drobiazko > http://tapestry5.de > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
