Yes, I just noticed that too. Need to comment out the javadoc dependencies from the root project. I really don't know enough of the gradle build to point out the underlying problem, but considering that even "gradle tasks" initially fails, it doesn't seem like we are using gradle quite right.
Kalle On Fri, Jun 10, 2011 at 7:43 PM, Richard Yunhua Sang <[email protected]> wrote: > I found the workaround is to disable the javadoc configuration first, then I > am able to build. After that, everything is back to normal even enable the > javadoc config. > > Richard > > On Fri, Jun 10, 2011 at 3:02 PM, Kalle Korhonen > <[email protected]>wrote: > >> On Fri, Jun 10, 2011 at 11:53 AM, Thiago H. de Paula Figueiredo >> <[email protected]> wrote: >> > On Fri, 10 Jun 2011 15:48:02 -0300, Kalle Korhonen >> > <[email protected]> wrote: >> >> Like it or not. While on Windows, I use bunch of stuff to make it >> >> behave more like Xnix to reduce my pain. >> > Cygwin? I just can't do any software development on Windows without it. >> > Fortunately, I can use Windows just for the games I can't run on Linux. >> :) >> >> That's given, with a bunch of aliases etc. Also >> https://sourceforge.net/projects/console/ to replace the idiotic >> Command Prompt. >> >> Kalle >> >> > >> > -- >> > Thiago H. de Paula Figueiredo >> > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, >> and >> > instructor >> > Owner, Ars Machina Tecnologia da Informação Ltda. >> > http://www.arsmachina.com.br >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
