os.detected.classifier not properly evaluated during gradle build.
See original GitHub issueI have the following compile dependency in my gradle file: ‘org.microbean:microbean-helm:2.8.2.1.0.4’. The build works without any issues when running gradle within Eclipse.
When the build is invoke from the command line (Gradle Version 4.1) I have the following errors:
Errors occurred while build effective model from /Users/yvdorego/.gradle/caches/modules-2/files-2.1/org.microbean/microbean-helm/2.8.2.1.0.4/44fb98754ff742b4a237718238bd9cced7906ffd/microbean-helm-2.8.2.1.0.4.pom:
'build.resources.resource.directory' is missing. in org.microbean:microbean-helm:2.8.2.1.0.4
Errors occurred while build effective model from /Users/yvdorego/.gradle/caches/modules-2/files-2.1/org.microbean/microbean-development-annotations/0.1.3/abaddafbff41cfff5f9332014aa30a7506498e6d/microbean-development-annotations-0.1.3.pom:
'build.resources.resource.directory' is missing. in org.microbean:microbean-development-annotations:0.1.3
Errors occurred while build effective model from /Users/yvdorego/.gradle/caches/modules-2/files-2.1/org.microbean/microbean-kubernetes/0.1.1/7fdace2d7ffa0c5e56e9f588ecc632a6333fe655/microbean-kubernetes-0.1.1.pom:
'build.resources.resource.directory' is missing. in org.microbean:microbean-kubernetes:0.1.1
FAILURE: Build failed with an exception.
> Could not find netty-tcnative-boringssl-static-${os.detected.classifier}.jar (io.netty:netty-tcnative-boringssl-static:2.0.6.Final).
Searched in the following locations:
https://repo1.maven.org/maven2/io/netty/netty-tcnative-boringssl-static/2.0.6.Final/netty-tcnative-boringssl-static-2.0.6.Final-${os.detected.classifier}.jar
As per above the os.detected.classifier
is not being resolved.
Any help will be greatly appreciated
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
java - Maven property not being evaluated as expected (os ...
I have seen problems with correctly resolving os.detected.classifier when my POM includes a parent POM that also defines os-maven-plugin to ...
Read more >Gradle 2.2.1 seems to ignore my classifier on my dependency ...
I will say that I'm new to gradle, but what I'm seeing does not seem normal. My build.gradle repositories looks like the following:....
Read more >os.detected.classifier not set - os-maven-plugin and eclipse ...
I know it is an old question, but I just ran into the same problem and found a solution that works for me....
Read more >os-maven-plugin 是设置各种有用属性(从OS 中检测的 ... - Gitee
Property: os.detected.classifier; Property: os.detected.release.* (Linux-only). Enabling os-maven-plugin on your Maven project; Using Gradle?
Read more >Using Gradle and the App Engine Plugin - Java 8
Add the following to your build.gradle file to add App Engine Gradle tasks, ... Additional information on Gradle can be found in App...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Just an FYI this is breaking SBT builds too. I worked around by explicitly referencing the dependency as was suggested.
Ex)
This should be documented.