[
https://issues.apache.org/jira/browse/MRESOLVER-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17633266#comment-17633266
]
ASF GitHub Bot commented on MRESOLVER-294:
------------------------------------------
michael-o commented on code in PR #221:
URL: https://github.com/apache/maven-resolver/pull/221#discussion_r1020882296
##########
src/site/markdown/api-compatibility.md:
##########
@@ -0,0 +1,113 @@
+# API Compatibility
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+Maven Resolver exposes 3 modules for clients and those extending Maven
Resolver:
Review Comment:
three
> 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)
