Rephrase myself. I will create a feature which provides the ability of changing JavaScript Interpretator at compiling time. Developers are totally free to choose whichever JavaScript Interpretator they like as long as its interface is the same as we currently using.
I shall write some documentation and scripts to give an introduction about how to choose JavaScript Interpretator they like. And only in this introduction I will use jsc-android [1] for demo purpose, but neither the source code or binary of Weex would contain any JavaScript interpretator code. I think this feature will not only solve the License and dependency problem for good, but also gives developers the ability of choosing JS interpretator they like. [1] https://www.npmjs.com/package/jsc-android Best Regards, York Shen 申远 > 在 2019年9月25日，14:56，York Shen <shenyua...@gmail.com> 写道： > > As it’s a NPM plugin, I need some time to figure out how to integrate it into > Android build process, but everything else should be fine. > > Best Regards, > York Shen > > 申远 > >> 在 2019年9月25日，14:49，York Shen <shenyua...@gmail.com >> <mailto:shenyua...@gmail.com>> 写道： >> >> Updated: >> >> I just found a JavasScript Interpretator callled jsc-android[1] under >> BSD-2-Clause License. As it’s provided the exactly same interface we are >> currently using, I think we can solve this problem by switching to >> jsc-android. >> >> Thanks for the help of @lucky-chen, I have successfully built and run Weex >> on jsc-android. >> >> No more platform dependency, no more LGPL runtime. >> >> [1] https://www.npmjs.com/package/jsc-android >> <https://www.npmjs.com/package/jsc-android> >> >> Best Regards, >> York Shen >> >> 申远 >> >>> 在 2019年7月23日，03:15，Myrle Krantz <my...@apache.org >>> <mailto:my...@apache.org>> 写道： >>> >>> Thanks YorkShen, >>> >>> This is an answer I can live with. Let's see if legal can live with it >>> too. I've pinged the ticket you made. Let me see if I can get it >>> unblocked. >>> >>> Best, >> >
