[osgi-dev] marking private packages

2013-08-09 Thread Raymond Auge
Hello, what is the proper way to mark private packages? I know of the bnd Private-Package header. Are there other ways? -- *Raymond Augé* http://www.liferay.com/web/raymond.auge/profile (@rotty3000) Senior Software Architect *Liferay, Inc.* http://www.liferay.com (@Liferay)

Re: [osgi-dev] marking private packages

2013-08-09 Thread BJ Hargrave
If a package is not exported, it is private. So there is no marking them private. Just don't export them. -- BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance hargr...@us.ibm.com office: +1 386 848 1781 mobile: +1 386 848 3788 From: Raymond Auge

Re: [osgi-dev] marking private packages

2013-08-09 Thread Raymond Auge
Right! On Fri, Aug 9, 2013 at 3:05 PM, BJ Hargrave hargr...@us.ibm.com wrote: If a package is not exported, it is private. So there is no marking them private. Just don't export them. -- *BJ Hargrave* Senior Technical Staff Member, IBM OSGi Fellow and CTO of the *OSGi Alliance*

Re: [osgi-dev] marking private packages

2013-08-09 Thread BJ Hargrave
x-internal *was* an Equinox thing. In Luna it is ignored. -- BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance hargr...@us.ibm.com office: +1 386 848 1781 mobile: +1 386 848 3788 From: Raymond Auge raymond.a...@liferay.com To: OSGi Developer Mail

Re: [osgi-dev] marking private packages

2013-08-09 Thread Thomas Watson
Equinox has always ignored the x-internal directive unless configured with the osgi resolver in 'strict' mode. By default the resolver mode was not strict. As BJ said, Equinox for Luna will no longer have an option for 'strict' mode so anything you export is treated the same and publically