From: Eero A. <eer...@ik...> - 2019-09-09 08:03:24
|
There is a use case that is related to the JAR split of Jython: Using Jython to create a sandboxed scripting environment. That use case would call for some more fine grained splitting of the Jython implementation. Policy permissions are granted by either by code signature or location https://docs.oracle.com/javase/8/docs/technotes/guides/security/PolicyFiles.html For the sandboxed scripting use case one would probably want to have the Jython class loader in it's own JAR in order to restrict class loading in there only. I understand a lot of more work would still be involved in serving this use case, but you could split this as a reservation, if a new jar layout is being taken into use. Eero Aaltonen On Sun, Sep 8, 2019 at 11:40 PM Jeff Allen <ja...@fa...> wrote: > I've noticed that the "project name" for the Gradle-built JAR cannot be > "jython", because we already publish that (being the fat jar). I propose > therefore to name it "jython-slim", in honour of this thread. > > It's experimental anyway: I don't have much confidence it is correctly > built. I could really do with writing an application with it as a > dependency. (Or others doing so during beta.) > > Jeff Allen > > On 21/05/2019 04:45, Adam Burke wrote: > > Hi Raphail > > > > The dev team are working on a gradle build, one of the outputs of > > which would be a slim jar as you describe. > > > > If you look on jython trunk, there is already an experimental > > build.gradle there. You may be able to use that to build an > > experimental jython-only jar. > > > > It's a complex part of the build, so if you know gradle well, I think > > patches are also welcome. > > > > Cheers > > Adam > > > |