First of all thanks for all the explanation. So If I understand well Rhino will be included because all the work is already done and it will be easier for the user. The version we use for now is 1.7.2 so no need for another CQ. So I guess that for Rhino there nothing else I need to do?
Regarding Jython this will be a “work with” because of licenses incompatibility. So I will have to launch a CQ later for this dependency. Is that it? Regards, Arthur Daussy Atos [email protected] +33 5 34 36 32 90 [LogoAtosPapyrus] De : [email protected] [mailto:[email protected]] De la part de John Arthorne Envoyé : jeudi 17 octobre 2013 16:02 À : E4 Project developer mailing list Objet : Re: [e4-dev] [EASE] "Work with" process 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 <[email protected]<mailto:[email protected]>> To: E4 Project developer mailing list <[email protected]<mailto:[email protected]>>, Date: 10/17/2013 09:51 AM Subject: Re: [e4-dev] [EASE] "Work with" process Sent by: [email protected]<mailto:[email protected]> ________________________________ On Thu, Oct 17, 2013 at 9:25 AM, DAUSSY Arthur <[email protected]<mailto:[email protected]>> 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 [email protected]<mailto:[email protected]> https://dev.eclipse.org/mailman/listinfo/e4-dev ________________________________ Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos ne pourra être engagée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être engagée pour tout dommage résultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
<<inline: image002.png>>
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
