[jira] [Commented] (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[
https://issues.apache.org/jira/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753625#comment-16753625
]
Sylwester Lachiewicz commented on MDEP-82:
--
Problem with jacoco-maven-plugin has been resolved with migration to plugin-api
3.0 - version 0.8.3 can be used in "offline mode"
For future reference:
artifacts from
https://github.com/apache/maven/blob/master/maven-core/src/main/resources/META-INF/maven/extension.xml#L128
list can generate problems
> 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)
[jira] [Commented] (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[
https://issues.apache.org/jira/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[
https://issues.apache.org/jira/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530067#comment-16530067
]
Antoine Morvan commented on MDEP-82:
Hi,
I'm experiencing issues also, with plugin version 3.1.1. I uploaded a small
example project to reproduce:
[https://github.com/antoine-morvan/resolve_plugin_issue]
Best.
> 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
>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)
[jira] [Commented] (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[
https://issues.apache.org/jira/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16492037#comment-16492037
]
Bob van der Linden commented on MDEP-82:
This is not yet fixed for me. Consider the following:
[https://gist.github.com/bobvanderlinden/960203d38475c4e0ffe861b049bbc107]
It fails with the following error:
{{[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-install-plugin:2.5.2:install (default-install)
on project main: Execution default-install of goal
org.apache.maven.plugins:maven-install-plugin:2.5.2:install failed: Plugin
org.apache.maven.plugins:maven-install-plugin:2.5.2 or one of its dependencies
could not be resolved: Cannot access central
(https://repo.maven.apache.org/maven2) in offline mode and the artifact
org.codehaus.plexus:plexus-container-default:jar:1.6 has not been downloaded
from it before. -> [Help 1] }}
> 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
>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)
[jira] [Commented] (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[
https://issues.apache.org/jira/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471815#comment-16471815
]
Hervé Boutemy commented on MDEP-82:
---
TL;DR = *Works with Maven 3.1.0+ and maven-dependency-plugin 3.3.0+, fails with
any Maven version or maven-dependency-plugin before*
If you have any issue, please precise which Maven and maven-dependency-plugin
versions you are using
Then detailed tests:
tested with attached pom.xml (dummy) and following settings.xml to provide a
clean local repository on each test (and locale repository manager for
efficiency):
{code:xml}
repo
{code}
then define explicitiely the maven-dependency-plugin version used for
{{go-offline}} to not depend on default version defined inside Maven:
{noformat}mvn -s settings.xml
org.apache.maven.plugins:maven-dependency-plugin:2.8:go-offline{noformat}
And finally check if the build in offline mode works:
{noformat}mvn -V -s settings.xml verify -o{noformat}
Result: build works with *maven-dependency-plugin starting with version 3.0.0*
with recent Maven versions
On one line:
{noformat}\rm -rf repo ; mvn -s settings.xml
org.apache.maven.plugins:maven-dependency-plugin:3.0.0:go-offline ; mvn -V -s
settings.xml verify -o{noformat}
works like a charm (tested with success also with 3.0.1, 3.0.2, 3.1.0)
The same test fails with 2.10 or anything before fails.
Tested with success with Maven 3.5.3, 3.3.9, 3.2.5, 3.1.0
But fails with Maven 3.0.5
> 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
>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)
[jira] [Commented] (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[
https://issues.apache.org/jira/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468912#comment-16468912
]
John commented on MDEP-82:
--
To narrow this down to versions.
maven = 3.5.2
{code:java}
mvn dependency:go-offline
mvn -o clean install{code}
Fails with missing poms for transitive dependencies of plugins:
{code:java}
--- jacoco-maven-plugin:0.8.0:prepare-agent (default-prepare-agent) @ my-lib ---
[WARNING] The POM for junit:junit:jar:4.8.2 is missing, no dependency
information available
[WARNING] The POM for org.apache.maven.reporting:maven-reporting-impl:jar:2.1
is missing, no dependency information available
[WARNING] The POM for org.jacoco:org.jacoco.agent:jar:runtime:0.8.0 is missing,
no dependency information available
[WARNING] The POM for org.jacoco:org.jacoco.core:jar:0.8.0 is missing, no
dependency information available
[WARNING] The POM for org.jacoco:org.jacoco.report:jar:0.8.0 is missing, no
dependency information available
{code}
1) junit is relied upon _somewhere_ in this build without being explicitly
listed anywhere.
2) the org.jacoco:org.jacoco.* dependencies _are_ listed explicitly by
org.jacoco, however, when resolved, they only pulled the .jar, not the .pom.
This led to the later failures.
But I noticed it was defaulting to using a slightly older
maven-dependency-plugin, 2.8. So i tried:
{code:java}
mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.0:go-offline
{code}
Forcing that version resolved _all_ transitive plugin dependencies properly!
However, I ran into further missing dependencies, specifically with surefire.
After explicitly adding those, I was able to build successfully.
So, there are several layers of dependency resolutions not occurring, depending
on the version of the plugin being used, and how other plugins are being
implemented. Definitely no easy answer here. Our company is committed to
getting this to work at the moment, so I'll probably continue to be bothersome
> 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
> Environment: Maven 2.0.6
>Reporter: Arne Degenring
>Priority: Major
> 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)
[jira] [Commented] (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[
https://issues.apache.org/jira/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467384#comment-16467384
]
John commented on MDEP-82:
--
Using Apache Maven 3.3.9, this error persists. Our build system uses a
"provision" step where all dependencies are gathered (we support a lot more
than Maven), and a build step in a clean environment with no internet
connectivity.
starting with a clean local repository:
{code:java}
repository jchittum$ pwd
/Users/jchittum/.m2/repository
repository jchittum$ ls
repository jchittum$
{code}
using the following POM
{code:java}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;>
4.0.0
com.akamai.devprod
pull-tester
jar
1.0-SNAPSHOT
test-app
https://dev-repos.devprod.akamai.com
junit
junit
4.8
test
com.spotify
docker-client
8.11.2
org.slf4j
slf4j-api
1.7.25
1.6
1.6
{code}
I then run go-offline, which populates a most plugins and dependencies,
however, I always run into some that aren't populated. Running mvn -o install
{code:java}
bos-mpoxc:test-pull-app jchittum$ mvn -o install
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building test-app 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
pull-tester ---
[WARNING] The POM for org.apache.maven:maven-core:jar:2.0.6 is missing, no
dependency information available
[WARNING] The POM for org.apache.maven:maven-monitor:jar:2.0.6 is missing, no
dependency information available
[WARNING] The POM for org.codehaus.plexus:plexus-utils:jar:2.0.5 is missing, no
dependency information available
[WARNING] The POM for org.apache.maven.shared:maven-filtering:jar:1.1 is
missing, no dependency information available
[WARNING] The POM for org.codehaus.plexus:plexus-interpolation:jar:1.13 is
missing, no dependency information available
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 0.525 s
[INFO] Finished at: 2018-05-08T07:52:34-05:00
[INFO] Final Memory: 9M/309M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-resources-plugin:2.6:resources
(default-resources) on project pull-tester: Execution default-resources of goal
org.apache.maven.plugins:maven-resources-plugin:2.6:resources failed: Plugin
org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies
could not be resolved: The following artifacts could not be resolved:
org.apache.maven:maven-profile:jar:2.0.6,
org.apache.maven:maven-repository-metadata:jar:2.0.6,
org.apache.maven:maven-plugin-registry:jar:2.0.6,
classworlds:classworlds:jar:1.1-alpha-2: Cannot access central
(https://repos.akamai.com/public-maven-repos) in offline mode and the artifact
org.apache.maven:maven-profile:jar:2.0.6 has not been downloaded from it
before. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
{code}
I can tell at least the following plugins are not downloaded with a go-offline:
* surefire (and transitive dependencies)
* jar (and its transitive dependencies
* compiler (and its transitive dependencies)
* resources (and its transitive dependencies)
It appears the original bug stating that core plugins for lifecycle phases are
not populated. As is, since our build environment is docker based, I'll be
setting up a script to manually pull all Apache maintained plugins and
populating the initial build environment.
How about this proposal?
The Maven Dependency Plugin, when using go-offline, should do a greedy pull,
and populate all Maven core plugins and their transitive dependencies.
> 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
> Environment: Maven 2.0.6
>Reporter: Arne Degenring
>Priority: Major
> Attachments: maven-dependency-plugin-2.3.patch, pom.xml
>
>
> The attached
[jira] [Commented] (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[
https://issues.apache.org/jira/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16432801#comment-16432801
]
Daniel commented on MDEP-82:
I'm running mvn 3.5.2, and I tried the workaround above. There's two issues,
one of which has its own workaround, but the other I haven't been able to work
out.
First off, when explicitly depending on the standard lifecycle plugins,
go-offline doesn't seem to be fetch transitive dependencies. The workaround is
to list them all explicitly. For example, in addition to listing
org.apache.maven.plugins:maven-compiler-plugin:3.6.1, also list what's below
(in xml, just colon separated for brevity):
# org.codehaus.plexus:plexus-utils:jar:2.0.4
# org.apache.maven:maven-repository-metadata:jar:3.0
# org.codehaus.plexus:plexus-component-annotations:jar:1.6
The second problem, and one that I don't have a fix for is that
org.apache.maven.plugins:maven-compiler-plugin:3.6.1 requires
org.apache.maven:maven-repository-metadata:jar:3.0, but
org.apache.maven.plugins:maven-resources-plugin:2.6 requires
org.apache.maven:maven-repository-metadata:jar:2.0.6. Listing both versions of
maven-repository-metadata gets me the 2.0.6 jar & pom, and the 3.0 pom, but no
jar. If I list them together using a range I get the same behavior.
Am I missing something here? Is there a workaround? A fix? Thank you in advance.
> 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
> Environment: Maven 2.0.6
>Reporter: Arne Degenring
>Priority: Major
> 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)
[jira] Commented: (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-tabpanelfocusedCommentId=279443#comment-279443 ] Paul Warren commented on MDEP-82: - Hi Folks, Ability (or inability) to go-offline is a showstopper for us. We have very large customers who state they have to have offline development. So naturally this was the goal I looked at first. One problem I have with it is the fact that it resolves top level dependencies only. It doesnt recursively descend through all subsequent transtive dependencies. I am new to maven but as that stands I don't see how it is adequate to actually solve the problem. But maybe I missed some fundamental concept. Anyway, I had a fiddle with the code and made is descend and resolve all transaitive dependencies and this was sufficient for my use case. I was then able to go-offline. I am going to attach the patch in case it helps others or you would like to fold it into the source. 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
[jira] Commented: (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-tabpanelfocusedCommentId=272920#comment-272920 ] Derek Lewis commented on MDEP-82: - Devin, I've used a similar situation to work around the problem. However, it means having to build everything, which is time consuming, and also means that commands you haven't run (like mvn deploy) won't work, because the deploy plugin wasn't downloaded. 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
[jira] Commented: (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-tabpanelfocusedCommentId=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
[jira] Commented: (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[ http://jira.codehaus.org/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=256614#action_256614 ] 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: http://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. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[ http://jira.codehaus.org/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94665 ] Brian Fox commented on MDEP-82: --- The problem is that the project isn't injected with the plugins from the standard lifecycle. I may have to hard code the standard ones (site,clean,default) until I can figure out how to get at the list directly. go-offline / resolve-plugins does not resolve all plugin dependencies - Key: MDEP-82 URL: http://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. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
