You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/11/12 17:00:00 UTC

[jira] [Commented] (MRESOLVER-294) Fix JapiCmp configuration and document it

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

ASF GitHub Bot commented on MRESOLVER-294:
------------------------------------------

cstamas opened a new pull request, #221:
URL: https://github.com/apache/maven-resolver/pull/221

   Fix japicmp configuration and explain what we "promise" to clients and what we "expect" from them.
   
   ---
   
   https://issues.apache.org/jira/browse/MRESOLVER-294




> Fix JapiCmp configuration and document it
> -----------------------------------------
>
>                 Key: MRESOLVER-294
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-294
>             Project: Maven Resolver
>          Issue Type: Task
>            Reporter: Tamas Cservenak
>            Assignee: Tamas Cservenak
>            Priority: Major
>             Fix For: 1.9.1
>
>
> Current japicm (add in 1.9.0) is to forgiving, it does not catches issues we thought it does.
> So we need to fix it.
> OTOH, we should also document what we "promise" to clients and what we "expect" from them regarding compatibility.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)