Re: [ANN] Apache Maven Dependency Analyzer Plugin 1.11.3 Released
> [MSHARED-949] - dependency:analyze should recommend narrower scope > where possible This sounds interesting. Two related questions: 1. Will dependency-managing the version to 1.11.3 make Maven Dependency Plugin automatically use the new feature? 2. Will there be a new release of Maven Dependency Plugin utilising the latest version of Maven Dependency Analyzer? Thanks in advance :-) -- Alexander Kriegisch https://scrum-master.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Dependency Analyzer Plugin 1.11.3 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Dependency Analyzer Plugin, version 1.11.3 This plugin analyzes the dependencies of a project for undeclared and unused artifacts. https://maven.apache.org/shared/maven-dependency-analyzer/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-dependency-analyzer 1.11.3 You can download the appropriate sources etc. from the download page: https://maven.apache.org/shared/maven-dependency-analyzer/download.cgi Release Notes - Maven Shared Components - Version maven-dependency-analyzer-1.11.3 Improvement [MSHARED-949] - dependency:analyze should recommend narrower scope where possible Task [MSHARED-948] - Update link to Jira Dependency upgrade [MSHARED-932] - Remove JMock dependency Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does POM have precedence over -D property expressions?
Hello,
While I do agree that it is not very intuitive, I don’t think there is any
chance to change this in a compatible way.
Also it’s pretty easy to understand: just remember this simplification: you
can only define properties, and if the configuration should be affected by them
you need to have a property explicitly in the POMs or as implicated default
value. With this info in mind Mojo Docs are much easier to read ;)
Gruß
Bernd
--
https://Bernd.eckenfels.net
Von: Andreas Sewe
Gesendet: Mittwoch, September 16, 2020 10:02 AM
An: users@maven.apache.org
Betreff: Re: Why does POM have precedence over -D property
expressions?
Andy Feldman wrote:
>> My situation is unfortunately a bit more complex than that, as I have
>> *two* s of the maven-enforcer-plugin, only one of which
>> should be affected by -DskipChecks. The other simply uses the
>> rule, which IMHO shouldn't easily be disabled (but
>> should still respect -Denforcer.skip)
>> [...]
>> What I want is this:
>> [...]
>
> -Denforcer.skip, being the more direct option, should
>> take precedence over -DskipChecks.
>
> Just an idea:
>
>
> false
> ${enforcer.skip}
>
>
> This way if you set -DskipChecks=true, then only checks would be
> skipped, but if you set -Denforcer.skip=true, it would also cause
> skipChecks to be true, so both executions would be skipped. I haven't
> actually tested it though.
Thanks, Andy. The above does have the desired behavior *if* the
maven-enforcer-plugin were the only plugin which should be governed by
-DskipChecks.
But as I said in my initial mail, that property should also control the
maven-checkstyle-plugin, maven-tidy-plugin, and others (kine of like
-DskipTests does for maven-surefire-plugin and maven-failsafe-plugin).
And that's just not doable with
${enforcer.skip}
I experimented quite a bit yesterday and have become convinced that the
desired behavior is not possible, at least without profiles (ugh!) --
and even then I am not sure, as the profile would need to affect only
some executions.
But maybe I am missing something.
Best wishes,
Andreas
Re: Why does POM have precedence over -D property expressions?
Andy Feldman wrote:
>> My situation is unfortunately a bit more complex than that, as I have
>> *two* s of the maven-enforcer-plugin, only one of which
>> should be affected by -DskipChecks. The other simply uses the
>> rule, which IMHO shouldn't easily be disabled (but
>> should still respect -Denforcer.skip)
>> [...]
>> What I want is this:
>> [...]
>
> -Denforcer.skip, being the more direct option, should
>> take precedence over -DskipChecks.
>
> Just an idea:
>
>
> false
> ${enforcer.skip}
>
>
> This way if you set -DskipChecks=true, then only checks would be
> skipped, but if you set -Denforcer.skip=true, it would also cause
> skipChecks to be true, so both executions would be skipped. I haven't
> actually tested it though.
Thanks, Andy. The above does have the desired behavior *if* the
maven-enforcer-plugin were the only plugin which should be governed by
-DskipChecks.
But as I said in my initial mail, that property should also control the
maven-checkstyle-plugin, maven-tidy-plugin, and others (kine of like
-DskipTests does for maven-surefire-plugin and maven-failsafe-plugin).
And that's just not doable with
${enforcer.skip}
I experimented quite a bit yesterday and have become convinced that the
desired behavior is not possible, at least without profiles (ugh!) --
and even then I am not sure, as the profile would need to affect only
some executions.
But maybe I am missing something.
Best wishes,
Andreas
signature.asc
Description: OpenPGP digital signature
