You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Marwa Khabbaz (Jira)" <ji...@apache.org> on 2020/12/15 16:07:00 UTC

[jira] [Created] (MPIR-400) mvn -pl . clean site site:stage fails when extensions are part of pom.xml

Marwa Khabbaz created MPIR-400:
----------------------------------

             Summary: mvn -pl . clean site site:stage fails when extensions are part of pom.xml
                 Key: MPIR-400
                 URL: https://issues.apache.org/jira/browse/MPIR-400
             Project: Maven Project Info Reports Plugin
          Issue Type: Bug
          Components: index, modules
    Affects Versions: 3.1.1, 3.1.0, 3.0.0
         Environment: Apache Maven Version: 3.6.3
Java version: 1.8.0_251, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk1.8.0_251\jre
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
            Reporter: Marwa Khabbaz
         Attachments: error_log.txt, pom_aggregator.xml, pom_sub-module.xml

I have a project consisting of an aggregator and a submodule, which inherits directly from the aggregator. I have the following scenarios:
 * When I execute {{mvn clean site site:stage}} (without {{-pl .}}), the build is successful.
 * When I leave out the extensions out of the {{pom.xml}}-file of my aggregator and execute the {{mvn -pl . clean site site:stage}}, the build is successful.
 * When I put in extensions to the {{pom.xml}}-file of my aggregator but leave out the reports for {{index}} and {{modules}} (the only sites that refer to my submodule) by explicitly defining the report set in the {{pom.xml}}-file of the aggregator, the build is successful.
 * As soon as I put extensions into the {{pom.xml}}-file of my aggregator and leave in the reports for {{index}} and {{modules}}, then execute the build {{mvn -pl . clean site site:stage}} for the aggregator, the build fails with a {{NullPointerException}}.

I attached the error log of the last scenario and the {{pom.xml}} of the aggregator and its submodule to this ticket. Hopefully I managed to understandably describe my issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)