Hello,
are Maven Enforcer (and Maven plugin in general) compatibility issues with
Maven 4 alpha-3 something that people should report or is it too early for
this? Should we wait at least for Maven beta release?
My current issue is with requirePluginVersion rule as demonstrated here -
https://gith
Hi,
Thanks for the info.
I'm working on the next version of Enforcer.
I added an issue to verify [1]
You can follow, add comments.
[1] https://issues.apache.org/jira/browse/MENFORCER-447
pt., 23 gru 2022 o 14:49 Pavel Horal napisał(a):
> Hello,
>
> are Maven Enforcer (and Maven plugin in ge
Please follow, comments
https://issues.apache.org/jira/browse/MENFORCER-447
pon., 19 gru 2022 o 17:53 Mirko Friedenhagen
napisał(a):
> Hello,
>
> we have configured this rule for ages and now when executing enforcer, I
> get:
>
> [INFO] --- enforcer:3.1.0:enforce (default-enforce) @ ---
>
Thank you. Will add comment with the requirePluginVersion issue.
Pavel
On Fri, 23 Dec 2022 at 15:17, Slawomir Jaranowski
wrote:
> Hi,
>
> Thanks for the info.
>
> I'm working on the next version of Enforcer.
>
> I added an issue to verify [1]
> You can follow, add comments.
>
> [1] https://issu
FYI I have tracked down the issue to Maven Model and
https://github.com/apache/maven/blob/e73a0b00fde80c400a6d854ec0c2ba7436325eed/maven-toolchain-model/src/main/mdo/reader.vm#L683
. Generated model reader is not setting location which is being used by
enforcer. Added this information to the issue.
Hello,
I have been using the copy-resources file for copying a configuration file
(log4j2.xml) from a shared source directory to the "target" directory.
${basedir}/../common/src/main/resources
${project.build.directory}
Burkhard Meier wrote:
> If I had a Jira account, I would create a bug to get this fixed (…)
I’m not sure if you already requested a Jira account, but if not, please note
that you can request a Jira account via the instructions on
https://issues.apache.org/jira/
Nils.
-
