gnodet commented on code in PR #2022: URL: https://github.com/apache/maven-resolver/pull/2022#discussion_r3705472080
########## src/site/markdown/what-is-resolver.md: ########## @@ -18,47 +18,16 @@ specific language governing permissions and limitations under the License. --> -Did you ever want to integrate Maven's dependency resolution mechanism -into your application and ended up trying to embed Plexus and an entire -Maven distribution? Did you ever want to use Maven's dependency -resolution mechanism in a multithreaded fashion and got burned by the -stateful singletons in there? Did you ever want to have a little more -control over how Maven calculates the resolved dependency graph, say use -another strategy for conflict resolution or inspect some intermediate -dependency graph? +Did you ever want to integrate the Maven dependency resolution mechanism into your application? Did you then try to embed Plexus and an entire Maven distribution? Did you want to use the mechanism in a multithreaded way? The stateful singletons in Maven caused problems. Did you ever want more control over the resolved dependency graph? For example, to can use another strategy for conflict resolution, or inspect an intermediate graph? +Did you ever want to integrate the Maven dependency resolution mechanism into your application? Did you then try to embed Plexus and an entire Maven distribution? Did you want to use the mechanism in a multithreaded way? The stateful singletons in Maven caused problems. Did you ever want more control over the resolved dependency graph? For example, to use another strategy for conflict resolution or inspect an intermediate graph? Review Comment: This paragraph appears to be a leftover — it's a duplicate of the corrected paragraph on the next line, but still contains the "to can use" grammar error. Deleting this line should fix it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
