${os.detected.classifier} cannot be resolved

[Eskibear]

From microsoft/vscode-maven#246 by @wensioness

---

${os.detected.classifier} cannot be resolved
at eclipse https://github.com/trustin/os-maven-plugin maybe available

project address: https://github.com/netty/netty.git

• OS: [Windows 10]
• VS Code version: [1.31.0]
• Extension version [0.14.0]

Screenshots

[fbricon]

as mentioned in https://github.com/trustin/os-maven-plugin#issues-with-eclipse-m2e-or-other-ides, this extension is not loaded by m2e.
It might be possible to load os-maven-plugin-1.6.1.jar as a java extension of jdt.ls though, but that'd require another vscode extension

[DachuanZhao]

Any progress ？

[pseudovector]

Got the same issue here

[jmhodges]

I think this is why some of the folks using protobuf-maven-plugin aren't having the protobuf generated resources added to vscode's understanding of the classpath. (And, so, they have to explicitly add it with builder-helper-maven-plugin.) Folks (like me) use <protocArtifact>com.google.protobuf:protoc:3.19.3:exe:${os.detected.classifier}</protocArtifact> to specify the protoc to use in the build. That causes vscode to bail even though it works correctly with

    <extensions>
      <extension>
        <groupId>kr.motd.maven</groupId>
        <artifactId>os-maven-plugin</artifactId>
        <version>1.7.0</version>
      </extension>
    </extensions>

in the <build>.

(This is also causing red squiggles in pom.xml, of course)

[jmhodges]

This seems to be a m2e bug, according to os-maven-plugin's README: https://github.com/trustin/os-maven-plugin#issues-with-eclipse-m2e-or-other-ides

[DachuanZhao]

According to https://stackoverflow.com/a/68660430/6862189 , you should add

<profiles>
  <profile>
    <id>os-properties</id>
    <properties>
      <os.detected.name>linux</os.detected.name>
      <os.detected.arch>x86_64</os.detected.arch>
      <os.detected.classifier>linux-x86_64</os.detected.classifier>
    </properties>
  </profile>
</profiles>

<activeProfiles>
  <activeProfile>os-properties</activeProfile>
</activeProfiles>

to maven setting file .

[AkashKumarIT]

adding this solved my problem

<dependency>
            <groupId>io.netty</groupId>
            <artifactId>netty-tcnative-boringssl-static</artifactId>
            <version>2.0.69.Final</version>
            <classifier>${os.detected.classifier}</classifier>
</dependency>

[Nyagar-Abraham]

I had the same issue trying to congire my webfux project with grpc and the solution was rather simple.
For IntelliJ IDEA:
- Click the Maven tab on the right side
- Click the refresh icon (🔄)
- The Reload all Maven projects
That fixed my issue.

[fbricon]

os-maven-plugin properties have been resolved by default for some time.

Closing.