Apparently missing dependency macro in bnd-maven-plugin 3.2.0

[Benson Margulies]

I'm not opening an issue in case I'm being dense.

In the pom:

<dependency>
    <groupId>com.basistech.osgi.template</groupId>
    <artifactId>rosette-osgi-template-component-core</artifactId>
    <version>${project.version}</version>
    <!-- We don't want our osgi bundle to pull in a maven
         dependency on the non-osgi modules when consumed.
         Note that this dependency will still show up in maven
         dependency:tree.
    -->
    <optional>true</optional>
</dependency>

In bnd.bnd:

-includeresource: \
   lib/=${com.basistech.osgi.template:rosette-osgi-template-component-core:jar};lib:=true

Result:

[WARNING] /Users/benson/x/rosette-osgi/template/component/osgi/bnd.bnd [0:0]: No translation found for macro: com.basistech.osgi.template:rosette-osgi-template-component-core:jar

Same result with and without the optional element.

[BJ Hargrave]

`${com.basistech.osgi.template:rosette-osgi-template-component-core:jar}` is not a legitimate bnd macro value. See http://bnd.bndtools.org/chapters/850-macros.html for a list of macros (although that list needs updating.)

--
You received this message because you are subscribed to the Google Groups "bndtools-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bndtools-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

--
BJ

[Benson Margulies]

As usual, nothing like posting a request to make the solution jump out. I lost the invocation of the dependency plugin to set the properties.

[Benson Margulies]

On Tuesday, July 26, 2016 at 8:36:26 AM UTC-4, BJ Hargrave wrote:

`${com.basistech.osgi.template:rosette-osgi-template-component-core:jar}` is not a legitimate bnd macro value. See http://bnd.bndtools.org/chapters/850-macros.html for a list of macros (although that list needs updating.)

Well, actually, it is with the bnd-maven-plugin, which propagates all the maven properties. 

[BJ Hargrave]

Only because you must have set that property somehow. That property is not set by the bnd-maven-plugin.

But glad you have your build working again!