i just found that the "problem" was introduced with FELIX-218
(BundlePlugin).
Before, this directive seemed not to be recognized at all. (was hard
coded written to Analyzer without brackets)
Toni Menzel schrieb:
hi,
building the current Main component breaks with this exception:
java.lang.IllegalArgumentException: key can't be empty
at java.lang.System.checkKey(System.java:742)
at java.lang.System.getProperty(System.java:625)
at aQute.lib.osgi.Macro.replace(Macro.java:84)
at aQute.lib.osgi.Macro.process(Macro.java:38)
at aQute.lib.osgi.Macro.process(Macro.java:25)
at aQute.lib.osgi.Builder.copy(Builder.java:313)
at aQute.lib.osgi.Builder.copy(Builder.java:308)
at aQute.lib.osgi.Builder.doIncludeResources(Builder.java:233)
at aQute.lib.osgi.Builder.build(Builder.java:31)
..
It turns out the its because of this line in the pom.xml:
<Include-Resource>{src/main/resources/}</Include-Resource>
The "http://cwiki.apache.org/FELIX/bundle-plugin-for-maven-bnd.html";
documentation says:
[..] If a resource clause is specified inside of "{ ... }" brackets,
then variable substitution will be performed on the resource, where
variables in the resources are denoted with "${ ... }" syntax. [..]
Seems like it could be handled more graceful my bnd (just ommit
substitution if there is nothing to substitute).
On the other hand the brackets {} should be ommitted anyway. At least
this works.
btw: is there a public svn repository for bnd to look at previous
versions? (because the pom from felix hasn't changed in the past but
bnd did) <-- probably a question for Peter..
regards,
Toni
--
Toni Menzel
http://www.tonit.com
mailto:[EMAIL PROTECTED]
