You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mark (JIRA)" <ji...@codehaus.org> on 2012/02/22 17:14:03 UTC
[jira] (MDEP-82) go-offline / resolve-plugins does not resolve all
plugin dependencies
[ https://jira.codehaus.org/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292446#comment-292446 ]
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 tests...
Try:
git clone https://github.com/cometd/cometd.git
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: https://jira.codehaus.org/browse/MDEP-82
> 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:
> [ERROR] BUILD 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira