Tests fail when maven-resolver-api is added to dependency-plugin

2020-07-02 Thread Ian Lavallee
I have a working verbose tree dependency graph builder in its own project currently that I am trying to now integrate within the dependency plugin. After adding maven-resolver-api:1.4.2 and not changing anything else mvn verify fails with errors similar to: 1) Error injecting: org.apache.maven.sh

Re: maven-compat in public API

2020-07-02 Thread Robert Scholte
The migration guide is about plugins, not about libraries. For libraries it can be tricky. However, based on  https://mvnrepository.com/artifact/org.apache.maven.shared/maven-shared-io [https://mvnrepository.com/artifact/org.apache.maven.shared/maven-shared-io]  the usage is quite low. There are

maven-compat in public API

2020-07-02 Thread Elliotte Rusty Harold
MSHARED-931 is a specific example of a problem I've run into in many plugins while trying to upgrade to Maven 3. https://issues.apache.org/jira/projects/MSHARED/issues/MSHARED-931 Per https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies part of this work is t

Re: Failing integration test MNG-6386 (Unicode chars) on macOS

2020-07-02 Thread Maarten Mulders
Hi Olivier, Please refer to MNG-6951 [1] where Michael did some further investigation. Thanks, Maarten [1] https://issues.apache.org/jira/browse/MNG-6951 On 02/07/2020 10:46, Olivier Lamy wrote: > Hi > I reckon to have been lazy and not reported it but I have this > failure locally. > But fail

Re: Failing integration test MNG-6386 (Unicode chars) on macOS

2020-07-02 Thread Olivier Lamy
Hi I reckon to have been lazy and not reported it but I have this failure locally. But fail for me as well. there is maybe some gitattributes to setup for this directory? On Thu, 2 Jul 2020 at 02:41, Maarten Mulders wrote: > On 01/07/2020 15:21, Michael Osipov wrote: > > Am 2020-07-01 um 11:25 s