[jira] [Closed] (MPIR-377) Profiles in POMs do not appear to be evaluated

["Robert Scholte (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MPIR-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MPIR-377.
-------------------------------
    Resolution: Not A Problem
      Assignee: Robert Scholte

Not sure which MNG issue fixed this, but the solution is: use at least Maven 3.6.0

> 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
>            Assignee: Robert Scholte
>            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)