maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Derek Lewis (JIRA)" <>
Subject [jira] Commented: (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
Date Thu, 17 Feb 2011 17:47:22 GMT


Derek Lewis commented on MDEP-82:

This issue has been open with no comment for a long time.  Is there really no fix or workaround
with the problem?  I'm required to package a zip of the ~/.m2/repository directory with our
software, including all dependencies needed to build from behind a strict corporate firewall.
 This bug is causing a great deal of grief for me.  Is this fixed in maven 3?

> go-offline / resolve-plugins does not resolve all plugin dependencies
> ---------------------------------------------------------------------
>                 Key: MDEP-82
>                 URL:
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Bug
>          Components: go-offline, resolve-plugins
>    Affects Versions: 2.0-alpha-4
>         Environment: Maven 2.0.6
>            Reporter: Arne Degenring
>            Assignee: Brian Fox
>         Attachments: 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:
> [INFO] ------------------------------------------------------------------------
> [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not exist or
no valid version could be found
> Afterwards, even "mvn package" without the "-o" parameter does not work any longer.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message