[jira] [Commented] (LOG4J2-3241) log4j-api-java9.pom and log4j-core-java9.pom sometimes cause maven enforcer to fail

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460311#comment-17460311 ] 

ASF subversion and git services commented on LOG4J2-3241:
---------------------------------------------------------

Commit a7f3d8c2261bcbde873903ee14135247b33189b6 in logging-log4j2's branch refs/heads/release-2.x from Ralph Goers
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=a7f3d8c ]

LOG4J2-3241 - Do not declare log4j-api-java9 and log4j-core-java9 as depdendencies as it causes problems with the Maven enforcer plugin


> log4j-api-java9.pom and log4j-core-java9.pom sometimes cause maven enforcer to fail
> -----------------------------------------------------------------------------------
>
>                 Key: LOG4J2-3241
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3241
>             Project: Log4j 2
>          Issue Type: Story
>          Components: Build
>    Affects Versions: 2.16.0
>            Reporter: Ralph Goers
>            Priority: Major
>
> Log4j API and Log4j Core have to build the Java 9 classes in one Maven module and then copy them into the "normal" module. The Java 9 projects are not deployed during a release. The pom.xml files were specifying both as provided dependencies. When the enforcer plugin sees this it is trying to resolve them - sometimes - and fails. It seems these don't need to be declared as dependencies because they are configured into the dependency plugin. So the dependencies should be removed from the pom files.



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