[
https://jira.codehaus.org/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271956#comment-271956
]
Devin Reid commented on MDEP-82:
--------------------------------
A workaround I have found for this issue is to run a build with the property
'maven.repo.local' set to a directory in the project base directory and run a
build to the install phase. One can then archive the resulting project and move
it to environments that have no network access and be able to build
successfully with the '-o' option.
I've tested this successfully with Maven 2.2.1 and Maven 3.0.3.
First run:
mvn -Dmaven.repo.local=lib clean install
Now the following command will work just fine.
mvn -Dmaven.repo.local=lib -o clean 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: 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
