[Commented] (MENFORCER-313) requireUpperBoundDeps: add [<scope>] and colors to the output

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Commented] (MENFORCER-313) requireUpperBoundDeps: add [<scope>] and colors to the output

JIRA jira@apache.org

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

ASF GitHub Bot commented on MENFORCER-313:
------------------------------------------

belingueres opened a new pull request #38: [MENFORCER-313] - Added [<scope>] to the conflicting artifacts in the output. Highlight those with compile scope.
URL: https://github.com/apache/maven-enforcer/pull/38
 
 
   [MENFORCER-313] - Added [<scope>] to the conflicting artifacts in the output.
   Highlight those with compile scope for easy reading.
   
   Following this checklist to help us incorporate your
   contribution quickly and easily:
   
    - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MENFORCER) filed
          for the change (usually before you start working on it).  Trivial changes like typos do not
          require a JIRA issue.  Your pull request should address just this issue, without
          pulling in other changes.
    - [ ] Each commit in the pull request should have a meaningful subject line and body.
    - [ ] Format the pull request title like `[MENFORCER-XXX] - Fixes bug in ApproximateQuantiles`,
          where you replace `MENFORCER-XXX` with the appropriate JIRA issue. Best practice
          is to use the JIRA issue title in the pull request title and in the first line of the
          commit message.
    - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
    - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will
          be performed on your pull request automatically.
   
   If your pull request is about ~20 lines of code you don't need to sign an
   [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
   please ask on the developers list.
   
   To make clear that you license your contribution under
   the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
    - [ x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
    - [x ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[hidden email]


> requireUpperBoundDeps: add [<scope>] and colors to the output
> -------------------------------------------------------------
>
>                 Key: MENFORCER-313
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-313
>             Project: Maven Enforcer Plugin
>          Issue Type: Improvement
>          Components: Standard Rules
>    Affects Versions: 3.0.0-M2
>            Reporter: Gabriel Belingueres
>            Priority: Minor
>              Labels: up-for-grabs
>         Attachments: eclipse-output.png, output.txt
>
>
> Hi:
> I checked the very maven-enforcer project using the new CLI functionality:
> mvn org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-SNAPSHOT:enforce -Drules=requireUpperBoundDeps
> and found out there is a conflicting library (org.codehaus.plexus:plexus-container-default). See output.txt.
> The tricky thing is that is it a transitive dependency, one with scope "compile", the other is scope "test" (which are not shown in the output). In contrast, Eclipse shows the scope and shaded fonts for the libraries with test scope (see screenshot image), which provide an easier reading.
> Regards,
> Gabriel



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)