Re: RFR: 8152818: Javadoc must support module options supported by javac.

2016-04-11 Thread Martin Buchholz
I think we can work -modulesourcepath into our build.xml CVS has zero support for symlinks, but at build time we can create a skeletal directory modulesrc/ modulesrc/java.base -> ${src.dir} or if necessary copy the entire tree when running javadoc. We're reluctant to reorganize our src/main direct

Re: RFR: 8152818: Javadoc must support module options supported by javac.

2016-04-11 Thread Jonathan Gibbons
On 04/11/2016 04:12 PM, Martin Buchholz wrote: On Mon, Apr 11, 2016 at 3:57 PM, Jonathan Gibbons wrote: On 04/07/2016 10:04 PM, Martin Buchholz wrote: I'm not really qualified, but here are random comments: I think the general idea is right - javac and javadoc need the same kind of support

Re: RFR: 8152818: Javadoc must support module options supported by javac.

2016-04-11 Thread Martin Buchholz
On Mon, Apr 11, 2016 at 3:57 PM, Jonathan Gibbons wrote: > > > On 04/07/2016 10:04 PM, Martin Buchholz wrote: >> >> I'm not really qualified, but here are random comments: >> >> I think the general idea is right - javac and javadoc need the same >> kind of support for modules. >> I worry that deta

Re: RFR: 8152818: Javadoc must support module options supported by javac.

2016-04-11 Thread Jonathan Gibbons
On 04/07/2016 10:04 PM, Martin Buchholz wrote: I'm not really qualified, but here are random comments: I think the general idea is right - javac and javadoc need the same kind of support for modules. I worry that details may be different, e.g. javadoc has diamond inheritance and pulls in via @