[xwiki-devs] OSGi manifest data for our core modules - xwiki-devs@xwiki.org - lists.xwiki.org

List overview All Threads
Download

[xwiki-devs] OSGi manifest data for our core modules

[xwiki-devs] [VOTE] Improve...

[xwiki-devs] Need tempresource...

Vincent Massol

23 May 2010 23 May '10

3:50 p.m.

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

Reply

Show replies by date

Sergiu Dumitriu

23 May 23 May

4:13 p.m.

On 05/23/2010 03:50 PM, Vincent Massol wrote:

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?

+1 -- Sergiu Dumitriu http://purl.org/net/sergiu/

Reply

Jerome Velociter

4:23 p.m.

+1 Jerome. ----- Original Message ----- From: "Sergiu Dumitriu" <sergiu(a)xwiki.com> To: "XWiki Developers" <devs(a)xwiki.org> Sent: Sunday, May 23, 2010 4:13:27 PM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna Subject: Re: [xwiki-devs] OSGi manifest data for our core modules On 05/23/2010 03:50 PM, Vincent Massol wrote:

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?

+1 -- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Reply

Thomas Mortagne

8 p.m.

+1 On Sun, May 23, 2010 at 15:50, Vincent Massol <vincent(a)massol.net> wrote:

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 devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

-- Thomas Mortagne

Reply

Marius Dumitru Florea

24 May 24 May

11:53 a.m.

+1 Thanks, Marius On 05/23/2010 04:50 PM, Vincent Massol wrote:

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 devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Reply

Guillaume Sauthier

25 May 25 May

9:56 a.m.

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... --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 devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Reply

Vincent Massol

10:08 a.m.

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

Reply

5228

days inactive

5230

days old

xwiki-devs@xwiki.org

Manage subscription

6 comments

6 participants

tags (0)

participants (6)

Guillaume Sauthier
Jerome Velociter
Marius Dumitru Florea
Sergiu Dumitriu
Thomas Mortagne
Vincent Massol