On May 25, 2010, at 9:56 AM, Guillaume Sauthier wrote: > May I point you to this interesting whitepaper that describes a semantic way > to handle versioning in OSGi ? > http://www.osgi.org/wiki/uploads/Links/SemanticVersioning.pdf > > I would advise to version your API and do not export internal implementation > details...
Thanks Guillaume. I think we're already do this to large extent but I'd love to have your opinion on it: - we already version all our artifacts with the strategy described in the PDF (major, minor, bug fix). We even use CLIRR in several places to ensure we don't introduce backward-compat regressions. Now we do *voluntarily* introduce some from time to time in minor releases. It's a tradeoff that we've accepted. I guess we could be less lenient there if need be in the future. IMO it depends on maturity of modules and we shouldn't be too rigid. - we already have the notion of "internal" package for implementation details - the maven-bundle -plugin automatically version Export-package values and automatically exclude internal packages AFAIK. There's one domain where your help would be awesome: to help review that manifest data generated by the maven-bundle-plugin and to help us with best-practices in this domain. I'm pretty sure the data generated by the maven-bundle-plugin could be improved. Thanks a lot. We do need help with OSGi since we're newbies in this domain so your help is most appreciated :) -Vincent > --G > > Le 23/05/2010 15:50, Vincent Massol a écrit : >> Hi devs, >> >> I'd like to add OSGi manifest data generation for our core modules during >> our build. >> >> This would be the first step in allowing xwiki modules to be used in an osgi >> environment (whether it's by us later on or by external users who want to >> use the xwiki rendering for example). >> >> WDYT? >> >> Thanks >> -Vincent _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
