Re: [xwiki-devs] [Discussion] Should our components be user-public or not?

Hi, We need to decide if we want our component implementations (the class implementing the interface of a component) to be user-public or not. By user-public I mean allowing user of the code to use them (for composition, for inheritance). The alternative is to make them internal and forbid users to import them. This means moving them to an internal package (see http://www​.eclipse.o​rg/article​s/ article.​php?file=A​rticle-API​-Use/index​.html) and telling our users that they change anytime so they shouldn't use them. This would also mean we wouldn't have to go through a deprecation stage to make any change to our components. My initial reaction to this was that they should be public but the more I think about it the more I think making them internal might be the best choice. WDYT? Thanks -Vincent _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs