projects _always_ export all packages. Is this a law/requirement?
I doubt that this is enforced in any way. In some cases you have packages that are internal to your bundle and you really want to prevent them from being called from other places. In that case there's no reason to export. IMO, it's just another level of visibility control and since private methods and package private classes are certainly allowed, why not bundle private packages?
Yes, I am fine with that but how can you test these packages if they are invisible from other plugins.
You can test them by using fragments instead of test plug-ins. As a fragment is always attached to a host plug-in and as they are loaded by the same classloader, you can test internal packages without exporting them. In addition to that you can create dependencies to test frameworks e.g. Mockito or JUnit in the manifest of the test fragment and keep the plug-in's manifest test framework free.
Regards, Eugen
Am Jan 13, 2010 um 18:12 schrieb Wim Jongman:
projects _always_ export all packages. Is this a law/requirement?
I doubt that this is enforced in any way. In some cases you have packages that are internal to your bundle and you really want to prevent them from being called from other places. In that case there's no reason to export. IMO, it's just another level of visibility control and since private methods and package private classes are certainly allowed, why not bundle private packages?
Yes, I am fine with that but how can you test these packages if they are invisible from other plugins.
Regards,
Wim
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
|
