| Re: [ebr-dev] Bundle Naming |
Gunnar has it exactly right: we don’t want to change the package names — ideally these recipes could/would disappear once we’ve helped fix the bundles upstream. But we do want to indicate provenance. This is a problem I’ve encountered with many of the Orbit bundles whose upstream have now provided properly- (or sometimes improperly-) bundlefied jars. I wonder if we couldn’t put the EBR prefix into the version qualifier instead? The downside is that it doesn’t help when rebundling existing broken jars. I can’t create a feature/product and have absolute certainty that the fixed EBR bundle will be included. In terms of naming, my preference is to use a bundle suffix of ‘.ebr’. It allows the bundles to sort naturally, and IDE helpers that support searching with partial-matching by bundle prefix, such as PDE’s Open Artifacts (Ctrl-Shift-A), works too. I used to get confused as to whether a product used javax.mail as I normally used the SpringSource com.springsource.javax.mail variant. Ideally we could make the naming policy configurable: the BSN doesn’t have to match the Maven EBR artifact, right? Brian.
|