Yep - the current snapshot of the bundle-plugin adds 'src/main/resources'
to the BND directives using Include-Resource, instead of using the target
path which has the filtered files.
There's an open bug (http://issues.apache.org/jira/browse/FELIX-261) to
address this issue, and also use maven configured resources instead of
a hard-coded location - see patch attached to FELIX-261.
I've been using this patch in the OPS4J branch of the bundle plugin (used
for testing patches and new features) and it seems to work ok, but would
appreciate if someone from Maven (Carlos?) could check it over.
Until then, workaround is to provide your own Include-Resource setting :(
On 09/05/07, Costin Leau <[EMAIL PROTECTED]> wrote:
Hi,
I'm not sure if it's me but I've noticed that resource filtering doesn't
work any more if bundle packaging is used.
If I have a file inside src/main/resources with a property:
Hello ${name}, with bundle packaging, the 'unexpanded' version is
included in the jar while the expanded version (Hello this is the name)
from target/classes is ignored.
Cheers,
--
Costin
--
Cheers, Stuart
