I have never had both problems when used mavn-dependency-plugin:2.8. With such older version it's ok?
On Sat, Oct 14, 2017 at 2:12 PM, Benedikt Ritter <brit...@apache.org> wrote: > Hello, > > > Am 13.10.2017 um 21:32 schrieb Tibor Digana <tibordig...@apache.org>: > > > > This exception is expected. > > Use pluginGroup in settings.xml or try this: > > org.codehaus.mojo:tidy:1.0.0:check > > or > > org.codehaus.mojo:tidy-maven-plugin:1.0.0:check > > > > I don't know what dummy.jar has to do with tidy plugin, it's internal > code > > in surefire due to M2 API and tidy should not be influenced by. > > There are to distinct issues: > > 1) surefire does some trickery which can not be resolved by the dependency > plugin. > 2) the tidy plugin does not work in offline mode, even if dependencies > have been downloaded before. Why do I have to define the plugin explicitly > to work in offline mode? It does work in online mode. > > Regards, > Benedikt > > > > > Cheers > > Tibor > > > > On Fri, Oct 13, 2017 at 6:36 PM, Benedikt Ritter <brit...@apache.org> > wrote: > > > >> Hello, > >> > >>> Am 08.10.2017 um 15:54 schrieb Hervé BOUTEMY <herve.bout...@free.fr>: > >>> > >>> Le dimanche 8 octobre 2017, 15:37:54 CEST Benedikt Ritter a écrit : > >>>> Hello Hervé > >>>> > >>>>> Then I added a pluginManagement section to select version 3.0.2 and > >> re-ran > >>>>> the test: you'll see the output is completely different. > >>>>> > >>>>> And there is no issue any more > >>>> > >>>> Thank you so much, you took the time to investigate this issue! Really > >> much > >>>> appreciated. Now I wonder, why Maven uses an outdated version of the > >>>> dependency plugin. Is this a problem with the super pom? > >>> this is a choice to keep stability: > >>> if one downloads dependencies using Maven 3.0.5 then a few days later > >> builds > >>> offline with Maven 3.5, he does not have any issue (and blame > >> dependency-plugin) > >>> > >>> remember the good practice: define your plugin versions, either in your > >> pom or > >>> by using a parent that does the job > >>> > >>>> > >>>> Furthermore I’ve noticed, that mvn -o test still does not work, > because > >> some > >>>> surefire dependencies are missing: > >>>> > >>>> [ERROR] Failed to execute goal > >>>> org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test > >> (default-test) > >>>> on project dependency-plugin-bug: Unable to generate classpath: > >>>> org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundExcep > tion: > >>>> Missing: [ERROR] ---------- > >>>> [ERROR] 1) org.apache.maven.surefire:surefire-junit3:jar:2.12.4 > >>>> [ERROR] > >>>> [ERROR] Try downloading the file manually from the project website. > >>>> [ERROR] > >>>> [ERROR] Then, install it using the command: > >>>> [ERROR] mvn install:install-file -DgroupId=org.apache.maven.surefire > >>>> -DartifactId=surefire-junit3 -Dversion=2.12.4 -Dpackaging=jar > >>>> -Dfile=/path/to/file [ERROR] > >>>> [ERROR] Alternatively, if you host your own repository you can deploy > >> the > >>>> file there: [ERROR] mvn deploy:deploy-file > >>>> -DgroupId=org.apache.maven.surefire -DartifactId=surefire-junit3 > >>>> -Dversion=2.12.4 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] > >>>> -DrepositoryId=[id] [ERROR] > >>>> [ERROR] Path to dependency: > >>>> [ERROR] 1) dummy:dummy:jar:1.0 > >>>> [ERROR] 2) org.apache.maven.surefire:surefire-junit3:jar:2.12.4 > >>>> [ERROR] > >>>> [ERROR] ---------- > >>>> [ERROR] 1 required artifact is missing. > >>>> [ERROR] > >>>> [ERROR] for artifact: > >>>> [ERROR] dummy:dummy:jar:1.0 > >>>> [ERROR] > >>>> [ERROR] from the specified remote repositories: > >>>> [ERROR] central (https://repo.maven.apache.org/maven2, releases=true, > >>>> snapshots=false) [ERROR] -> [Help 1] > >>>> [ERROR] > >>>> [ERROR] To see the full stack trace of the errors, re-run Maven with > >> the -e > >>>> switch. [ERROR] Re-run Maven using the -X switch to enable full debug > >>>> logging. [ERROR] > >>>> [ERROR] For more information about the errors and possible solutions, > >> please > >>>> read the following articles: [ERROR] [Help 1] > >>>> http://cwiki.apache.org/confluence/display/MAVEN/ > MojoExecutionException > >>>> > >>>> Since there are only a few dependencies missing, I will run test not > in > >>>> offline modus on my CI server. But I wonder whether this is a bug. > >>> I'll have a look at this one and report > >> > >> I made another interesting observation: > >> > >> mvn tidy:check works, while mvn -o tidy:check does not work. It fails > with: > >> > >> [INFO] ------------------------------------------------------------ > >> ------------ > >> [INFO] BUILD FAILURE > >> [INFO] ------------------------------------------------------------ > >> ------------ > >> [INFO] Total time: 0.640 s > >> [INFO] Finished at: 2017-10-13T18:34:32+02:00 > >> [INFO] Final Memory: 13M/309M > >> [INFO] ------------------------------------------------------------ > >> ------------ > >> [ERROR] No plugin found for prefix 'tidy' in the current project and in > >> the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] > available > >> from the repositories [local (/Users/bene/workspace/github/ > dependency-plugin-bug/.m2), > >> central (https://repo.maven.apache.org/maven2)] -> [Help 1] > >> [ERROR] > >> [ERROR] To see the full stack trace of the errors, re-run Maven with the > >> -e switch. > >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. > >> [ERROR] > >> [ERROR] For more information about the errors and possible solutions, > >> please read the following articles: > >> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ > >> NoPluginFoundForPrefixException > >> > >> Cheers, > >> Benedikt > >> > >>> > >>> Regards, > >>> > >>> Hervé > >>> > >>>> > >>>> Regards, > >>>> Benedikt > >>>> > >>>>> Regards, > >>>>> > >>>>> Hervé > >>>>> > >>>>> Le mercredi 20 septembre 2017, 22:48:15 CEST Benedikt Ritter a écrit > : > >>>>>> Hi, > >>>>>> > >>>>>> as far as I understand it should be possible to call mvn > >>>>>> dependency:go-offline and from there on work in offline mode (mvn > -o). > >>>>>> I’ve put a minimal example together [1] that demonstrates that this > >>>>>> currently does not work. Am I missing anything? > >>>>>> > >>>>>> Thank you! > >>>>>> Benedikt > >>>>>> > >>>>>> [1] https://github.com/britter/dependency-plugin-bug > >>>>>> > >>>>>> > >>>>>> ------------------------------------------------------------ > --------- > >>>>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >>>>>> For additional commands, e-mail: dev-h...@maven.apache.org > >>>>> > >>>>> ------------------------------------------------------------ > --------- > >>>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >>>>> For additional commands, e-mail: dev-h...@maven.apache.org > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >>>> For additional commands, e-mail: dev-h...@maven.apache.org > >>> > >>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >>> For additional commands, e-mail: dev-h...@maven.apache.org > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> For additional commands, e-mail: dev-h...@maven.apache.org > >> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Cheers Tibor
