Bnds source code is always included in the jar. Most old versions can
be found on http://www.aqute.biz/repo/biz/aQute/bnd
I'll check for empty macros ... Notice that it is not me exploding but
the System properties. :-) However, I'll make sure it does not happen.
Kind regards,
Kind regards,
Peter Kriens
TM> hi,
TM> building the current Main component breaks with this exception:
TM> java.lang.IllegalArgumentException: key can't be empty
TM> at java.lang.System.checkKey(System.java:742)
TM> at java.lang.System.getProperty(System.java:625)
TM> at aQute.lib.osgi.Macro.replace(Macro.java:84)
TM> at aQute.lib.osgi.Macro.process(Macro.java:38)
TM> at aQute.lib.osgi.Macro.process(Macro.java:25)
TM> at aQute.lib.osgi.Builder.copy(Builder.java:313)
TM> at aQute.lib.osgi.Builder.copy(Builder.java:308)
TM> at aQute.lib.osgi.Builder.doIncludeResources(Builder.java:233)
TM> at aQute.lib.osgi.Builder.build(Builder.java:31)
TM> ..
TM> It turns out the its because of this line in the pom.xml:
TM> <Include-Resource>{src/main/resources/}</Include-Resource>
TM> The "http://cwiki.apache.org/FELIX/bundle-plugin-for-maven-bnd.html";
TM> documentation says:
TM> [..] If a resource clause is specified inside of "{ ... }" brackets,
TM> then variable substitution will be performed on the resource, where
TM> variables in the resources are denoted with "${ ... }" syntax. [..]
TM> Seems like it could be handled more graceful my bnd (just ommit
TM> substitution if there is nothing to substitute).
TM> On the other hand the brackets {} should be ommitted anyway. At least
TM> this works.
TM> btw: is there a public svn repository for bnd to look at previous
TM> versions? (because the pom from felix hasn't changed in the past but bnd
TM> did) <-- probably a question for Peter..
TM> regards,
TM> Toni
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599
