pzygielo edited a comment on pull request #46: URL: https://github.com/apache/maven-dependency-plugin/pull/46#issuecomment-625871051
> Perhaps this is another separate issue related to `go-offline` changes? Perhaps it is. You can check [existing ones](https://issues.apache.org/jira/browse/MDEP-690?jql=%20project%20%3D%22Maven%20Dependency%20Plugin%22%20and%20component%20%3Dgo-offline%20) and if none covers your case you can submit new. But I think it is due to feature [MDEP-204: Transitively resolve both dependencies and plugins](https://issues.apache.org/jira/browse/MDEP-204) delivered in [3.1.2](https://github.com/apache/maven-dependency-plugin/releases/tag/maven-dependency-plugin-3.1.2) that exposes that [io.netty:netty-parent:4.1.49.Final](https://repo.maven.apache.org/maven2/io/netty/netty-parent/4.1.49.Final/netty-parent-4.1.49.Final.pom) (parent of dependency you use) references undefined `os.detected.name` and `os.detected.arch` properties. Try: ``` mvn dependency:go-offline -Dos.detected.name=linux -Dos.detected.arch=x86_64 ``` and you'll get all resolved. (Or use in your project the same build extension as netty-parent does - `kr.motd.maven:os-maven-plugin` to set them). ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
