[
https://issues.apache.org/jira/browse/MPOM-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MPOM-387:
---------------------------------
Component/s: maven
(was: asf)
Description:
In Maven Parent POM the enforcer {{enforceBytecodeVersion}} is added without
any special configuration, which IMHO is wrong.
For example, this rule prevents to use *Java 11 test-only dependencies* on a
project that is otherwise producing Java 8 artifact.
IMHO, applying this rule on everything makes no sense, at lest test scope
should be ignored (if not provided as well, as one have no control what is
provided).
was:
In ASF Parent POM the enforcer {{enforceBytecodeVersion}} is added without any
special configuration, which IMHO is wrong.
For example, this rule prevents to use *Java 11 test-only dependencies* on a
project that is otherwise producing Java 8 artifact.
IMHO, applying this rule on everything makes no sense, at lest test scope
should be ignored (if not provided as well, as one have no control what is
provided).
> Enforcer enforceBytecodeVersion applies to everything
> -----------------------------------------------------
>
> Key: MPOM-387
> URL: https://issues.apache.org/jira/browse/MPOM-387
> Project: Maven POMs
> Issue Type: Bug
> Components: maven
> Reporter: Tamas Cservenak
> Priority: Major
>
> In Maven Parent POM the enforcer {{enforceBytecodeVersion}} is added without
> any special configuration, which IMHO is wrong.
> For example, this rule prevents to use *Java 11 test-only dependencies* on a
> project that is otherwise producing Java 8 artifact.
> IMHO, applying this rule on everything makes no sense, at lest test scope
> should be ignored (if not provided as well, as one have no control what is
> provided).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
