maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark (JIRA)" <>
Subject [jira] (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
Date Wed, 22 Feb 2012 16:14:03 GMT


Mark commented on MDEP-82:

This issue is even more annoying for proper two-phase deployments where packages are built
on bare build systems without network access and where testing is done after the build on
the target platform: it absolutely makes no sense to execute the tests just to prepare the
package sources, but the tests won't have all dependencies later on when I don't execute the


git clone
cd cometd
git checkout 2.4.0
mvn -Dmaven.repo.local=/tmp/maven-repo dependency:go-offline
mvn -Dmaven.repo.local=/tmp/maven-repo -o install
> 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: 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:
> [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, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message