I seem to have discovered that the issue (for me) was in the parent/trunk pom.xml. The JavaDoc section had some split lines, which could have been messing up the parameter passing to the spawned javadoc @parameters, @options parameter files.
On 4 Nov 2010 at 12:32, Dan Haywood wrote: > ... just commited (rev 1030905); and now documented in [1]. > > Basically, Kevin came back to me last night and found a problem running > javadoc for the 'release' module (either by -D site=full or -D > build=full). Still don't know why that's the case, but at any rate it's > a bit of a pointless thing for us to build Javadoc for that module > anyway... (if you're not sure what it's for, it's basically to do define > a dependency with scope=import in an Isis app). >
