The distinction is whether you want to actually include/distribute Rhino, or require that the user install Rhino independently. If you are including Rhino that is easy as it is already approved for distribution in e4 and there is already a CQ so we are done. If you want this to be a dependency that the user installs separately then we would need a "Works With" dependency to document that. If that is what you want we can do that, although I think it is easier for the end user if we include Rhino in whatever feature provides the scripting support so they don't have an extra manual setup step.
John From: Paul Webster <pwebs...@alumni.uwaterloo.ca> To: E4 Project developer mailing list <e4-dev@eclipse.org>, Date: 10/17/2013 09:51 AM Subject: Re: [e4-dev] [EASE] "Work with" process Sent by: e4-dev-boun...@eclipse.org On Thu, Oct 17, 2013 at 9:25 AM, DAUSSY Arthur <arthur.dau...@atos.net> wrote: Hi All, In order to fully integrate EASE into E4 repository I have to ask you about “Work With” ( http://www.eclipse.org/org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf ). In order to use EASE, we need to “Work With Rhino engine to interpret Javascript (https://dev.eclipse.org/ipzilla/show_bug.cgi?id=3530). So I think the good process is to publish this on the mail list and get the approval of the PMC. Is that correct? Hi Arthur, If you want to use 1.7 R2 it looks like we've already met the process requirements for using it in eclipse.e4, and you're approved to go ahead with it. You can decide later if you want to move up to 1.7 R4 and we would need to open a new CQ. Sorry for the confusion. Later, Paul -- Paul Webster Hi floor. Make me a sammich! - GIR _______________________________________________ e4-dev mailing list e4-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________ e4-dev mailing list e4-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/e4-dev
