2009/2/17 Sahoo <[email protected]> > Naming convention varies from project to project, so I don't like to > define any rule that depend on them. Although I prefer everything as > private-package to everything as exported by default, I am actually fine if > you say everything is exported by default in order to ease migration to > OSGi. But, I definitely don't like the idea of relying on any naming > convention to decide what to export or not. > > If we want to delay the decision of making what should be the default, is > there any advantage in defining a variable or a macro (whatever fits the > nomenclature of the plugin) that denotes everything found in source dir? Let > user specify that as value of Export-Package or Private-Package. >
Maven is all about convention over configuration, so assuming that any packages marked "internal" or "impl" should be kept private is IMHO following this tradition. Not sure of the value in providing another macro containing the source list - if they want to export all the contents of the bundle without accidentally pulling in anything else they can always use <_exportcontents>*</_exportcontents> because this will then override the default export setting... Thanks, > Sahoo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Cheers, Stuart
