Haha yep. That makes more sense. People laugh at ny BlackBerry, but the auto correct is awesome.
Thanks! Nick Sent from my BlackBerry. I am AFK at the moment Original Message From: [email protected] Sent: Wednesday, November 26, 2014 3:04 PM To: [email protected] Reply To: [email protected] Subject: Re: Free-form Version Coercion to OSGi Compatible Version Hi Achim, I guess you mean: Karaf is using *bnd* under the hood. So you best take a look at the *bnd* tools. Gotta love those whacky spellcheckers ;-) Regards, Chris > Hi, > > Karaf is using and under the hood. > So you best take a look at the end tools. > > Regards, Achim > > sent from mobile device > Am 26.11.2014 16:54 schrieb "Nick Baker" <[email protected]>: > >> Hey All, >> >> We’ve written a deployer to transform WebJars >> (http://www.webjars.org) >> into bundles compatible with our RequireJS setup. Part of this process >> involves transforming the maven version into an OSGI Version. Most >> artifacts adhere to maven version standards, though some are just >> strings >> (SHAs, TRUNK-SNAPSHOT, etc.). I’ve written a simple parser to handle >> this. >> However, I’m noticing that Karaf or perhaps BND is doing the same >> version >> coercion. Can anyone point me to this class. I’m concerned I’m >> re-inventing >> the wheel and stumbling over the same edge cases. >> >> Here’s our VersionParser: >> >> https://github.com/pentaho/pentaho-osgi-bundles/blob/master/pentaho-webjars-deployer/src/main/java/org/pentaho/osgi/platform/webjars/VersionParser.java >> >> Thanks, >> -Nick Baker >> >
