They are evidence of past mistakes. They had packages which contained unrelated code. When the decided to split the bundle to partition the unrelated functions, they were forced to split the packages.
So the lesson is to design your packages wisely. They should have high cohesion. Don't put unrelated functions in the same package so that when you refactor bundles later, you are not forced to split packages :-( -- BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [email protected] office: +1 386 848 1781 mobile: +1 386 848 3788 From: Jin Mingjian <[email protected]> To: OSGi Developer Mail List <[email protected]> Date: 2010/05/15 00:19 Subject: Re: [osgi-dev] What are best practices for split packages across mutiple bundles Sent by: [email protected] Equinox seemly has some split packages in my memory. Are they necessary or history mistakes?:) _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
