[JXR-161] aggregate nofork regression

**[Delany](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=delany)** opened **[JXR-161](https://issues.apache.org/jira/browse/JXR-161?redirect=false)** and commented

Not sure why the issue component isnt just "maven jxr plugin"? Anyway, with v2.3 of the plugin I can run
 
    ./mvnw jxr:test-aggregate surefire-report:report-only
 
and I'll get a report in 10s. But when I update to v3.1.1 it takes forever invoking separate lifecycles as described in
https://maven.apache.org/jxr/maven-jxr-plugin/examples/nofork.html
 
The last sentence on that page "Note: These reports may not be used for aggregate reports." But this is exactly what I want, and since the behaviour was available I consider this a regression, no?

---

**Affects:** 3.1.1

Start by reproducing ./mvnw jxr:test-aggregate surefire-report:report-only with plugin versions 2.3 and 3.1.1, then read the nofork example linked in the issue. Trace why the newer version invokes separate lifecycles and determine whether aggregate reporting can retain the earlier behavior without the documented limitation.

Written by the indexing model from the issue text.