Hi Dale, this worked: --- One thing to perhaps try is to revert build.xml and add your new “quarks.samples.scenarios.iotf.range.sensor” package to the existing javadoc task param decl:
excludepackagenames="quarks.connectors.runtime,quarks.connectors.*.runtime,quarks.console.*,quarks.topology.spi.*,quarks.graph.spi.*" --- I thought I tried that, but I must have had something else broken at the time :-) Thank you so much for the help! I was flailing by this point... For anyone interested, take a look at the two build.xml's and the common-build.xml here: https://github.com/apache/incubator-quarks/pull/98/files for how to exclude a specific package from building and generating Javadoc. I also made it so that the build takes place if a PI4J_LIB environment variable is set. On Tue, Apr 19, 2016 at 10:05 AM, Dale LaBossiere <[email protected]> wrote: > Caveat: I’m not an “ant” wizzard :) > > At a high level, independent of the problem you’re encountering, the new > exclude of "samples/scenarios/src/main/java/quarks/samples/scenarios/**” > seems logically inappropriate since there's also the > quarks.samples.scenarios.iotf package and IotfFullScenario.java under that > dir which shouldn’t be excluded, right? > > One thing to perhaps try is to revert build.xml and add your new > “quarks.samples.scenarios.iotf.range.sensor” package to the existing > javadoc task param decl: > > > > excludepackagenames="quarks.connectors.runtime,quarks.connectors.*.runtime,quarks.console.*,quarks.topology.spi.*,quarks.graph.spi.*" > > Or perhaps revert build.xml and try changing the <sourcepath><dirset> to > use an “excludes” parameter instead of nested <exclude> element? e.g. > something like: > <sourcepath> > <dirset > excludes=“android/**,samples/scenarios/**/iotf/range/sensor”> > <include name=“*/*/src/main/java”/> > </dirset> > </sourcepath> > > I noticed the following in the ant javadoc task doc: > "Note: many problems with running javadoc stem from command lines > that have become too long - even though the error message doesn't give the > slightest hint this may be the problem. If you encounter problems with the > task, try to set the useexternalfile attribute to true first. > Maybe your changes triggered that problem?" > > There seem to be other general issues with the javadoc handling. There’s > a “Quarks SPI” group declared, but since the above is excluding the spi > packages, that group doesn’t get generated… and there’s no spi related > javadoc. But removing those spi exclusions causes the spi packages to > show up in the Quarks API group and that’s no good. > > Since that excludepackagenames has “quarks.connectors.*.runtime”, a single > level wildcard, the Quarks Connectors javadoc group ends up with > quarks.connectors.wsclient.javax.websocket.runtime. It should be > specifying a multi-level wildcard “**”. > > — Dale > > > On Apr 18, 2016, at 5:02 PM, Alexander Cook <[email protected]> wrote: > > > > > > Here is the latest comparison: > > > https://github.com/apache/incubator-quarks/compare/master...Alex-Cook4:master > > > > Thanks for the help! > > > > Here is what I'm using for the javadoc build now: > > > > <fileset dir="${basedir}"> > > <include name="*/*/src/main/java/*"/> > > <exclude name="android/**"/> > > <exclude > > name="samples/scenarios/src/main/java/quarks/samples/scenarios/**"/> > > </fileset> > > <packageset dir="${basedir}"> > > <include name="*/*/src/main/java/**"/> > > </packageset> > >
