# Add .JAR for using classes in Jython scripts **URL:** \ **Category:** 3rd Party Modules\ **Created:** [January 9, 2017, 10:37am UTC](https://forum.inductiveautomation.com/t/add-jar-for-using-classes-in-jython-scripts/12529 "2017-01-09T10:37:10Z")\ **Posts on this page:** 1\ **Showing post:** 17
**Author:** ![code\_skin](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@code\_skin](https://forum.inductiveautomation.com/u/code_skin)\ **Post date:** [May 2, 2019, 12:53pm UTC](https://forum.inductiveautomation.com/t/add-jar-for-using-classes-in-jython-scripts/12529/17 "2019-05-02T12:53:05Z")
Scripts. I'm working my way to building a module for it so users can use the system.\* namespace in there scripts. My end goal is to expose the apache poi 4.1.0 to end users. I've been digging around the forums and I'm wondering if my end goal is not possible? Kevin mentions a weird corner case about possible conflicts with the reporting module because it uses poi-3.14. > [@Adding java custom classes to Ignition](http://forum.inductiveautomation.com/t/adding-java-custom-classes-to-ignition/15202/18): > > I just unzipped the jar file for that version and looked. You’re going to run into the same potential conflict as long as the Reporting module is installed. You’ve hit a weird corner case in the architecture of the Client and Designer and its flat class path. If you loaded POI in the Gateway scope and all your interactions with the library took place there you’d be okay. I'm looking for a kick start in the right direction (Uninstalling the reporting module isn't an option for our client); is 4.1.0 not a good idea because of the reporting module? Is it a safer bet to use the same version as the reporting module? Is it possible to just access the existing POI library from all scopes? --- _[View the full topic](https://forum.inductiveautomation.com/t/add-jar-for-using-classes-in-jython-scripts/12529)._