Is there a dot in front of the path? "./libs/alljoyn.jar;version=file " ? Try removing that. Also i remember using version=FILE (all caps). Maybe you try this too. Don't know if this is case sensitive.
*Toni Menzel* *Developer Advocates - The Rebaze Way * *www.rebaze.de <http://www.rebaze.de/> | www.rebaze.com <http://www.rebaze.com/> | @rebazeio <https://twitter.com/rebazeio>* On Fri, Oct 21, 2016 at 9:46 AM, <manoj.vrajam...@wipro.com> wrote: > I did try this.... But it still did not take...saying invalid property > key.. (Put libs folder..just like in the same level as generated folder > in the package. > > Please take a look at my source file of bnd.bnd > > > > > # > # BUNDLE > # > > > Bundle-Version: 1.0.0.${tstamp} > Bundle-Description: \ > A bundle with a provider. Notice that this provider exports the API > package. \ > It also provides a JUnit test and it can be run standalone. \ > \ > ${warning;Please update this Bundle-Description in > com.wipro.iot.alljoyn.adapter/bnd.bnd} > > Private-Package: \ > com.wipro.iot.alljoyn.adapter > > -classpath:libs/alljoyn.jar;version=file > > Export-Package: com.wipro.iot.alljoyn.*;version=1.0 > > Import-Package: > > -buildpath: \ > osgi.enroute.base.api;version=1.0 > ./libs/alljoyn.jar;version=file --------------------------------------> > error line > > -testpath: \ > osgi.enroute.junit.wrapper;version=4.12 > > -includeresource: {readme.md} > > > -runrequires: \ > osgi.identity;filter:='(osgi.identity=com.wipro.iot.alljoyn.adapter)' > > -runbundles: \ > ${error;Resolve first} > > ------------------------------ > *From:* osgi-dev-boun...@mail.osgi.org <osgi-dev-boun...@mail.osgi.org> > on behalf of Timothy Ward <tim.w...@paremus.com> > *Sent:* 21 October 2016 12:26:05 > *To:* OSGi Developer Mail List > *Subject:* Re: [osgi-dev] Plain Jar to OSGi Bundle conversion > > > ** This mail has been sent from an external source ** > Manoj, > > You can add the jar file into a folder in your project and point at it > using a relative path and setting the version to be “file”, e.g. > > lib/toWrap.jar;version=file > > > Regards, > > Tim > > On 21 Oct 2016, at 07:46, manoj.vrajam...@wipro.com wrote: > > Hi all, > > I was trying the http://enroute.osgi.org/tutorial_wrap/200-project.html > tutorial > (for Plain Jar to OSGi Bundle conversion) > > The step is to add a local jar into the Build Path of bnd.bnd file. > > In fact, I was trying to add a local jar into the "Repository Local" (so > that it can be added later to the above Build Path of bnd.bnd ) but failed > because it does not accept plain jars and errors saying *Not a Bundle jar* > > How do I proceed from here ? What do I do ? > > Thanks, > Manoj > The information contained in this electronic message and any attachments > to this message are intended for the exclusive use of the addressee(s) and > may contain proprietary, confidential or privileged information. If you are > not the intended recipient, you should not disseminate, distribute or copy > this e-mail. Please notify the sender immediately and destroy all copies of > this message and any attachments. WARNING: Computer viruses can be > transmitted via email. The recipient should check this email and any > attachments for the presence of viruses. The company accepts no liability > for any damage caused by any virus transmitted by this email. > www.wipro.com_______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev > > > The information contained in this electronic message and any attachments > to this message are intended for the exclusive use of the addressee(s) and > may contain proprietary, confidential or privileged information. If you are > not the intended recipient, you should not disseminate, distribute or copy > this e-mail. Please notify the sender immediately and destroy all copies of > this message and any attachments. WARNING: Computer viruses can be > transmitted via email. The recipient should check this email and any > attachments for the presence of viruses. The company accepts no liability > for any damage caused by any virus transmitted by this email. > www.wipro.com > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev >
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
