Community
Participate
Working Groups
When trying to extend EMF Compare framework, one finds that many internal packages are not exported. This is kind of a show stopper of us extenders, and slows down API evolution toward user needs. A nice approach to let users play with internal stuff, but make them aware that it should be done "at their own risk" is to export packages and mark them as internal using the OSGi directive x-internal:=true I propose to export all the framework's internal packages and mark them as internal. x-friends directive should be used instead when some bundle is using an internal package of another bundle withing the framework (to avoid PDE warnings / compilation errors)
Patch against HEAD will be provided ASAP
Created attachment 200082 [details] patch v1 exported internal packages and marked as internal: - org.eclipse.emf.compare.match - org.eclipse.emf.compare.diff I've checked other bundles, and it doesn't seem to be necessary to export. What I haven't checked are the bundles from epatch and mpatch. If you guys want, I can check those too and provide another patch. Cheers, Víctor.
Comment on attachment 200082 [details] patch v1 The patche was missing the x-internal directive on one of the internal packages, making it public.
I have commited a modified version with all "internal" packages marked as such, as exporting two "public" packages I forgot from the UI.
(In reply to comment #4) > I have commited a modified version with all "internal" packages marked as such, > as exporting two "public" packages I forgot from the UI. Yeah, I left those intentionally public because I couldn't see the *internal* word in the namespace, so I assumed those where maybe forgotten or something. Thanks!
Oh, I see, that's right, I missed one! :P
