| [eclipse.org-architecture-council] Re-exporting dependency to fragment-provided third-party API |
| Hi, I am currently working on opening up the provisional API of GEF4 and I ran into a case where I need some (architectural) advice. We had not exposed any public API so far (all packages were exported with x-friends or x-internal declaratives), and we did thus not re-export any third-party dependencies either. We tried to depend on Orbit bundles (Google Guice, Google Guava) via version-constrained package-imports alone. As we now open up all our API, we have to introduce re-exports for those third-party dependencies that are exposed through our own API, which requires transferring the affected Orbit package-imports into require-bundles. While this is pretty much straightforward in most cases, there is one case that bothers me: we expose com.google.inject.multibindings.MapBinder, which is provided by an Orbit fragment (com.google.inject.multibindings), not by an Orbit bundle. I can thus not transform the related package-import into a require-bundle, and I do not see a chance to properly re-export this dependency either. Is there a recommendation on how to handle this case properly? Regards, Alexander -- Dr. Alexander Nyßen Dipl.-Inform. Principal Engineer Telefon: +49 (0) 231 / 98 60-202 Telefax: +49 (0) 231 / 98 60-211 Mobil: +49 (0) 151 / 17396743 http://www.itemis.de alexander.nyssen@xxxxxxxxx itemis AG Am Brambusch 15-24 44536 Lünen Rechtlicher Hinweis: Amtsgericht Dortmund, HRB 20621 Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens Trompeter, Sebastian Neus Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer Fiorentino |
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail