Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maven cannot download all depedencies with dependency:go-offline #3

Open
luizluca opened this issue Nov 29, 2016 · 3 comments
Open

Comments

@luizluca
Copy link

Hello,

I tried to get all maven dependencies with "mvn dependency:go-offline" in order to build without network. However, when I run "mvn -o compile", it still misses some dependencies:

##[WARNING] The POM for org.apache.maven:maven-plugin-api:jar:3.0 is missing, no dependency information available
##[WARNING] The POM for org.apache.maven:maven-core:jar:3.0 is missing, no dependency information available
##[WARNING] The POM for org.apache.maven:maven-artifact:jar:3.0 is missing, no dependency information available
##[WARNING] The POM for org.apache.maven:maven-settings:jar:3.0 is missing, no dependency information available
##[WARNING] The POM for org.apache.maven:maven-model:jar:3.0 is missing, no dependency information available
##[WARNING] The POM for org.codehaus.plexus:plexus-utils:jar:3.0.24 is missing, no dependency information available
##[WARNING] The POM for org.apache.maven.shared:maven-filtering:jar:3.1.1 is missing, no dependency information available
##[WARNING] The POM for org.codehaus.plexus:plexus-interpolation:jar:1.22 is missing, no dependency information available
##[WARNING] The POM for org.codehaus.plexus:plexus-component-annotations:jar:1.6 is missing, no dependency information available

And when those are provided, I keep getting other warnings about other artifacts.

It seems that pom.xml is not enough for informing maven about its dependencies.

I do not understand maven. That's why I'm opening this issue as you are the best ones to identify if this is a pom.xml or maven's one (or which version it should work).

@luizluca
Copy link
Author

luizluca commented Dec 2, 2016

These are all dependencies that I needed to "dependency:get", that "dependency:go-offline" missed, in order to build offline

org.apache.maven:maven-plugin-api:3.0 org.apache.maven:maven-core:3.0 org.codehaus.plexus:plexus-utils:3.0.24 org.codehaus.plexus:plexus-component-annotations:1.6 org.apache.maven.shared:maven-filtering:3.1.1 org.apache.maven.plugins:maven-resources-plugin:3.0.1 org.apache.maven:maven-plugin-api:2.2.1 org.apache.maven:maven-artifact:2.2.1 org.apache.maven:maven-core:2.2.1 org.apache.maven:maven-toolchain:2.2.1 org.apache.maven.shared:maven-shared-utils:0.7 org.apache.maven.shared:maven-shared-incremental:1.1 org.codehaus.plexus:plexus-compiler-api:2.5 org.codehaus.plexus:plexus-compiler-manager:2.5 org.codehaus.plexus:plexus-compiler-javac:2.5 org.apache.maven.plugins:maven-compiler-plugin:3.3 org.apache.maven:maven-plugin-api:3.0.3 org.apache.maven:maven-core:3.0.3 com.google.guava:guava:10.0.1 org.apache.maven.surefire:maven-surefire-common:2.19.1 org.apache.maven.surefire:surefire-api:2.19.1 org.apache.maven.surefire:surefire-junit4:2.19.1 org.codehaus.plexus:plexus-archiver:2.6.3 org.codehaus.plexus:plexus-utils:3.0.18 org.apache.maven.plugins:maven-source-plugin:2.4 org.apache.maven.shared:maven-invoker:2.0.9 org.apache.maven.shared:maven-common-artifact-filters:1.3 org.apache.maven.doxia:doxia-sink-api:1.4 org.apache.maven.doxia:doxia-site-renderer:1.4 commons-lang:commons-lang:2.4 commons-io:commons-io:2.2 org.apache.httpcomponents:httpclient:4.2.3 commons-logging:commons-logging:1.1.1 log4j:log4j:1.2.14 com.thoughtworks.qdox:qdox:1.12.1 org.codehaus.plexus:plexus-archiver:2.9 org.codehaus.plexus:plexus-utils:3.0.20

Maybe some of them depends on each other but they might give a hint on what is missing

@RangerRick
Copy link

Weird. Those are all things internal to maven, pulled in by core plugins and such.

I've not tried to do "offline" builds of any of our maven stuff in a long time, so I don't really have any experience with why go-offline would not handle those.

@j-white
Copy link

j-white commented Dec 5, 2016

One method I've used in the past for grabbing all of the dependencies is to:

  1. Wipe the local Maven repository rm -rf ~/.m2/repository
  2. Build
  3. Look at the artifacts in ~/.m2/repository, those were either required by, or produced by the build

That said, we don't really have any requirements for building offline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants