On 2010-12-01, at 3:26 PM, Marcel Offermans wrote: > Well, there can obviously be a difference between the "deployment view" for a > project, where you have only a single copy of such utility classes (in other > words, I'm totally against making copies of the source code here) and how to > package the sources into bundles, the "deployment view". So with only one > source copy, which gets compiled and included into each bundle that uses it I > feel you get the best of both worlds: no duplication of source code and no > coupling at deployment time.
Right I was assuming no source duplication (that would be a nightmare!). Even so, we likely have dozens if not a hundred bundles that use some of these utility classes. In many cases there is no build that does them all and they are on different release cycles and ... So actually propagating changes is a challenge as it means rebuilding and redeploying all the bundles not just one. > But I totally agree, there is a balance here, and there is no generic answer. > :) Absolutely. The topics I mentioned are "things to watch for" not "nails in the coffin". Jeff _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
