[jira] [Created] (MNG-6288) Metadata for Dependency Management Entries
Daniel Heinrich created MNG-6288:
Summary: Metadata for Dependency Management Entries
Key: MNG-6288
URL: https://issues.apache.org/jira/browse/MNG-6288
Project: Maven
Issue Type: New Feature
Components: Design, Patterns & Best Practices
Reporter: Daniel Heinrich
Priority: Minor
You will have a lot of version conflicts of transitive dependencies in a normal
project. These conflicts will get resolved by maven automatically, but most of
the time you want your team to explicitly decide on the conflict resolution.
This decision has to be placed in the dependency management section.
Over time dependencies change and therefor their transitive dependencies too.
The problem is now, that while out decisions(in form of dependency management
entries) stay the basis of the past decisions have changed.
There is no automatic way at the moment to check for dependency management
entries which need to be updated, because the conflict they try to resolve has
changed.
I propose to add the option to add some kind of meta data to dependency
management entries, which can be used by some plugin to report on decisions
which have to be reworked.
An example could be:
{code:xml}
org.slf4j
slf4j-api
1.4.0
1.3.0,1.3.2
{code}
or more generic:
{code:xml}
org.slf4j
slf4j-api
1.4.0
1.3.0,1.3.2
...
{code}
I hope this will spark some sort of discussion, because I think Maven can still
do a lot to support changes to a project over time way better.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MNG-6218) Jansi 1.3 does not recognize MinGW bash
[ https://issues.apache.org/jira/browse/MNG-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Heinrich updated MNG-6218: - Description: Jansi checks if the platform is Windows to decide if coloring needs to be handled differently. In the case that MinGW is detected it will handle coloring as if it was running on Unix. The test in Jansi 1.3 is if the enviroment variable TERM == "xterm", but MinGW returns "xterm-256color". Since Jansi 1.4 it checks if TERM starts with "xterm". see: https://github.com/fusesource/jansi/blob/jansi-project-1.14/jansi/src/main/java/org/fusesource/jansi/AnsiConsole.java#L123 An upgrade to Jansi 1.4 or even 1.5 fixes this issue. was: Jansi use checks if the platform is Windows to decide if coloring needs to be handled differently. In the case that MinGW is detected it will handle coloring as if it was running on some Unix. The test in Jansi 1.3 is if the enviroment variable TERM == "xterm", but MinGW returns "xterm-256color". Since Jansi 1.4 it checks if TERM starts with "xterm". see: https://github.com/fusesource/jansi/blob/jansi-project-1.14/jansi/src/main/java/org/fusesource/jansi/AnsiConsole.java#L123 An upgrade to Jansi 1.4 or even 1.5 fixes this issue. > Jansi 1.3 does not recognize MinGW bash > --- > > Key: MNG-6218 > URL: https://issues.apache.org/jira/browse/MNG-6218 > Project: Maven > Issue Type: Bug > Components: Command Line >Affects Versions: 3.5.0 > Environment: Windows Git Bash(MinGW) >Reporter: Daniel Heinrich >Priority: Minor > Original Estimate: 24h > Remaining Estimate: 24h > > Jansi checks if the platform is Windows to decide if coloring needs to be > handled differently. In the case that MinGW is detected it will handle > coloring as if it was running on Unix. > The test in Jansi 1.3 is if the enviroment variable TERM == "xterm", but > MinGW returns "xterm-256color". > Since Jansi 1.4 it checks if TERM starts with "xterm". > see: > https://github.com/fusesource/jansi/blob/jansi-project-1.14/jansi/src/main/java/org/fusesource/jansi/AnsiConsole.java#L123 > An upgrade to Jansi 1.4 or even 1.5 fixes this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MNG-6218) Jansi 1.3 does not recognize MinGW bash
Daniel Heinrich created MNG-6218: Summary: Jansi 1.3 does not recognize MinGW bash Key: MNG-6218 URL: https://issues.apache.org/jira/browse/MNG-6218 Project: Maven Issue Type: Bug Components: Command Line Affects Versions: 3.5.0 Environment: Windows Git Bash(MinGW) Reporter: Daniel Heinrich Priority: Minor Jansi use checks if the platform is Windows to decide if coloring needs to be handled differently. In the case that MinGW is detected it will handle coloring as if it was running on some Unix. The test in Jansi 1.3 is if the enviroment variable TERM == "xterm", but MinGW returns "xterm-256color". Since Jansi 1.4 it checks if TERM starts with "xterm". see: https://github.com/fusesource/jansi/blob/jansi-project-1.14/jansi/src/main/java/org/fusesource/jansi/AnsiConsole.java#L123 An upgrade to Jansi 1.4 or even 1.5 fixes this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
