[
https://issues.apache.org/jira/browse/MRESOLVER-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17633335#comment-17633335
]
Hudson commented on MRESOLVER-294:
----------------------------------
Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » master #82
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/master/82/
> Fix JapiCmp configuration and document it
> -----------------------------------------
>
> Key: MRESOLVER-294
> URL: https://issues.apache.org/jira/browse/MRESOLVER-294
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> 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)
