[MJAVADOC-732] Use javax.tools API for calling javadoc

**[Konrad Windszus](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kwin)** opened **[MJAVADOC-732](https://issues.apache.org/jira/browse/MJAVADOC-732?redirect=false)** and commented

Currently javadoc is called as external process which makes consuming/exposing warnings and errors a bit cumbersome and also prevents proper m2e integration.

As https://openjdk.org/jeps/106 added javadoc support to `javax.tools` with Java 8 it should be safe to adopt that given that m-javadoc-p has been updated to require Java 8 in MJAVADOC-675

---

**Issue Links:**
- [MJAVADOC-756](https://issues.apache.org/jira/browse/MJAVADOC-756) Use ToolProvider API, not CLI to invoke javadoc
(_**"is duplicated by"**_)

2 votes, 4 watchers

Start by locating where the plugin currently invokes javadoc as an external process and review the javax.tools API introduced for javadoc in Java 8. Compare the related MJAVADOC-756 issue, which duplicates this request. Done means javadoc is invoked through the API so warnings and errors can be consumed and m2e integration is no longer blocked.

Written by the indexing model from the issue text.