On Tue, 2009-01-20 at 10:33 +0100, Hans Dockter wrote: > On Jan 17, 2009, at 12:10 PM, Russel Winder wrote: > > > Perhaps it is just me but I find getting all the JavaDoc errors about > > missing packages at the start of Gradle build very annoying. Can't > > the > > errors relating to Gradle classes be removed by only doing a JavaDoc > > after a compile (i.e. make the javadoc task depend on compile) and to > > include all the generated class files on the javadoc task classpath? > > I find them also annoying. I think those warnings are a strong hint > that we need to refactor our packaging. We need to do this anyway for > our move to OSGi. So I hope we get rid of the warnings soon.
I tried the experiment of making the javadoc task depend on the compile task, and of course it failed as there is no way of setting the classpath for the javadoc task -- which is needed to include the classes of Groovy sources in the parsing. So until the JavaDoc task is fixed properly, there seems no hope to getting rid of the messages. GRADLE-360 sets out one of the issues, but there are many others. I probably won't be able to get stuck in to this in the next week or so (nor the Ant task, I'm afraid) -- a paying job has come up and it is Python oriented, and I cannot afford to give up on anything that gives me some income. -- Russel. ==================================================== Dr Russel Winder Partner Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203 41 Buckmaster Road, f: +44 8700 516 084 London SW11 1EN, UK. m: +44 7770 465 077
signature.asc
Description: This is a digitally signed message part
