Community
Participate
Working Groups
Comply with "Eclipse.org policy on use of 3rd party dependencies":http://www.eclipse.org/org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf Though it's up to the PMC, according to the policy, we likely fall under the "prerequisite" category, which requires: * PMC must document prerequisite dependency ** discussion about prerequisite versus "works with" must be transparent * Additions to IP log to indicate dependency * PMC must review issues wrt license compatibility - hopefully we can piggy-back off the work that was done for SWT * EMO must declare/approve dependency - again, can we just piggy-back off SWT? * EMO must determine if it falls into "exempt" prerequisite category ** this should be a no-brainer, since Windows is listed as an example of an exempt prerequisite ** if exempt, it doesn't require IP review The search component (see bug 349351) would like to make use of JNI to access Winows APIs, specifically: * msado15.dll * afx.h * afxwin.h * afxext.h * afxdtctl.h * afxcmn.h * windows.h * iostream * jni.h * SDKDDKVer.h
this component is also linking against MFC
Sounds like we are good here and don't need a separate CQ: http://dev.eclipse.org/mhonarc/lists/mylyn-pmc/msg00081.html.
Thanks Steffen, that's great news.
are we ok to go ahead with a pre-req, or does this have to be a works-with?
My understanding is that it's an "exempt prerequisite" so we can proceed without additional paperwork.
Great, thanks
