Ah. Never mind. I found https://github.com/trustin/os-maven-plugin/issues/34 .
> -----Original Message----- > From: m2e-users <m2e-users-boun...@eclipse.org> On Behalf Of KARR, DAVID > Sent: Monday, April 11, 2022 11:13 AM > To: m2e-users@eclipse.org > Subject: [m2e-users] How to do something like "os-maven-plugin" that > works with m2e? > > *** Security Advisory: This Message Originated Outside of AT&T ***. > Reference http://cso.att.com/EmailSecurity/IDSP.html for more > information. > > I'm looking at a project with a dependency like this: > --------------------- > <dependency> > <groupId>io.netty</groupId> > <artifactId>netty-tcnative</artifactId> > <version>2.0.20.Final</version> > <classifier>${os.detected.classifier}</classifier> > <scope>runtime</scope> > </dependency> > ---------------- > > That "os.detected.classifier" property is generated at build time with > this: > --------------- > <extension> > <groupId>kr.motd.maven</groupId> > <artifactId>os-maven-plugin</artifactId> > <version>1.5.0.Final</version> > </extension> > --------------- > > This works fine from the command line. In Eclipse, this fails with > errors indicating that "${os.detected.classifier}" doesn't get populated > with a value. > > Is there a reasonable strategy for moving this forward? Is there a > different way of determining the platform classifier that is more > compatible with m2e? > _______________________________________________ > m2e-users mailing list > m2e-users@eclipse.org > To unsubscribe from this list, visit > https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/m2e > - > users__;!!BhdT!l1RfC4p80s95dF1cPf7nMg2KsAEIhxSrxQeOPXMfaGvCqGQTUVmYs3pVI > zWa8U0Ww3XLynFCTMw$ _______________________________________________ m2e-users mailing list m2e-users@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/m2e-users
