[
https://issues.apache.org/jira/browse/MNG-7071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261522#comment-17261522
]
Robert Scholte commented on MNG-7071:
-------------------------------------
Looking at the PR I see most changes in maven-compat. In general we shouldn't
touch maven-compat anymore as it should be dead code and is only there for
backwards compatibility for Maven2 based plugins.
So -1 to accept the PR.
Instead I suggest to drop maven-compat for Maven 4 and introduce a new module
called maven-compat3, where we can put classes that should not be used by
Maven4 code, but are there for backwards compatibility for Maven 3
> Remove warning about ignored profiles.xml
> -----------------------------------------
>
> Key: MNG-7071
> URL: https://issues.apache.org/jira/browse/MNG-7071
> Project: Maven
> Issue Type: Improvement
> Components: Profiles
> Reporter: Martin Kanters
> Priority: Minor
> Labels: tech-debt
>
> Maven 2 had support for a profiles.xml, which allowed for profile
> configuration. In Maven 3 this support is removed (in favor of specifying
> that config in pom.xml or settings.xml) and a warning is triggered when there
> is a profiles.xml detected. The warning specifies that the profiles.xml file
> is ignored.
> With the introduction of Maven 4 I think we should remove this warning and
> all code related to it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)