You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by Marshall Schor <ms...@schor.com> on 2010/08/03 23:31:30 UTC

problem with property substitution within in maven-bundle-plugin:bundle

 In my build I set the build final name for some things using

<finalName>a.b.c_${parsedVersion.osgiVersion}</finalName>

where ${parsedVersion.osgiVersion} is a parameter value set by executing the
maven-build-helper plugin which is the first plugin run when the build executes
(I checked this and observed it, using the -X debug flag).

If I use the maven-jar-plugin to build the jar, it gets the value of
"finalName", which, I suspect, is
"a.b.c_${parsedVersion.osgiVersion}" and then changes it by substituting the
value of that property, so it comes out something like

"a.b.c_2.3.1".

This works fine (it's just what I want) when I use the maven-jar-plugin.

However, I'm now using for some projects the maven-bundle-plugin.  This plugin,
when it is given the same string, appears to not rescan it for variables, and
does not therefore substitute values.  So, its "bundle" goal works, but
generates the artifact using the name "a.b.c_${parsedVersion.osgiVersion}",
which is, obviously, not what I need.

Is this a known issue, and is there a good work-around for it?

-Marshall Schor

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org