[ https://issues.apache.org/jira/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16735337#comment-16735337 ]
Sylwester Lachiewicz commented on MDEP-82: ------------------------------------------ For [~antoine-morvan] sample project issue is with org.apache.maven.plugin.internal.PluginDependencyResolutionListener#isWagonProvider where old 2.x Maven's Wagon was excluded from dependences. I hope after org.jacoco:jacoco-maven-plugin will be updated to 3+ API it can be solved. > go-offline / resolve-plugins does not resolve all plugin dependencies > --------------------------------------------------------------------- > > Key: MDEP-82 > URL: https://issues.apache.org/jira/browse/MDEP-82 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: go-offline, resolve-plugins > Affects Versions: 2.0-alpha-4, 2.8, 2.10 > Environment: Maven 2.0.6 > Reporter: Arne Degenring > Assignee: Sylwester Lachiewicz > Priority: Major > Fix For: 3.0.0 > > Attachments: maven-dependency-plugin-2.3.patch, pom.xml > > > The attached pom.xml is a very simple JAR project, without any direct > dependencies or plugin dependencies. > Start with an empty local repository, and run mvn dependency:go-offline on > it. Some files get downloaded, but not everything that is needed for the > build. If you run "mvn -o package" afterwards, you end up with the following > error: > {noformat}[ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not > exist or no valid version could be found{noformat} > Afterwards, even "mvn package" without the "-o" parameter does not work any > longer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)