[
https://issues.apache.org/jira/browse/MPIR-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701292#comment-16701292
]
Gabriel Belingueres commented on MPIR-377:
------------------------------------------
Hi Jason.
I could reproduce the stacktrace with Maven 3.5.4, but running with Maven 3.6.0
there is no exception.
Can you confirm this in your own environment?
> Profiles in POMs do not appear to be evaluated
> ----------------------------------------------
>
> Key: MPIR-377
> URL: https://issues.apache.org/jira/browse/MPIR-377
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
> Affects Versions: 3.0.0
> Environment: Maven 3.5.4, Win 32_64, Java 10
> Reporter: Jason Faust
> Priority: Minor
> Attachments: log.txt, pom.xml
>
>
> First of, I do not know if this is a bug, or if it's a result of OpenJFX
> being silly with how they setup their parent pom (
> [http://repo.maven.apache.org/maven2/org/openjfx/javafx/11.0.1/javafx-11.0.1.pom]
> and
> [http://repo.maven.apache.org/maven2/org/openjfx/javafx-base/11.0.1/javafx-base-11.0.1.pom]
> ), and the bug should be filed there, but:
> The dependencies report reports warnings of the OpenJFX poms (for example)
> referring to themselves, as they depend on {{${javafx.profile}}} having a
> value, which is derived from the parent POM. Net result is it appears that
> the dependencies report is unable to see the full tree, whereas Maven
> normally is able to include all of the jars required for a build.
> Error triggered by running 'site' against the attached [^pom.xml].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
