You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Delany (Jira)" <ji...@apache.org> on 2021/12/13 08:29:00 UTC

[jira] [Created] (JXR-161) aggregate nofork regression

Delany created JXR-161:
--------------------------

             Summary: aggregate nofork regression
                 Key: JXR-161
                 URL: https://issues.apache.org/jira/browse/JXR-161
             Project: Maven JXR
          Issue Type: Bug
          Components: maven2 jxr plugin
    Affects Versions: 3.1.1
            Reporter: Delany


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?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)