# Adding java custom classes to Ignition

**URL:** <https://forum.inductiveautomation.com/t/adding-java-custom-classes-to-ignition/15202>\
**Category:** General Discussion\
**Tags:** sdk, ignition79, scripting\
**Created:** [August 30, 2017, 3:06pm UTC](https://forum.inductiveautomation.com/t/adding-java-custom-classes-to-ignition/15202 "2017-08-30T15:06:37Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 30, 2017, 3:17pm UTC](https://forum.inductiveautomation.com/t/adding-java-custom-classes-to-ignition/15202/2 "2017-08-30T15:17:45Z")

</div>

The only way to do this is to drop your jar files into the `lib/core/gateway`, `lib/core/client`, `lib/core/designer`, or `lib/core/common` folders, depending on the scope you want to be able to access them in. Putting them in common should make them available everywhere. The downside is that these are not part of the backup or preserved in any way, so you need to make sure your jars are always added to those locations in new gateways, etc… on your own.

disclaimer: this is not officially supported and there are no guarantees this will continue working in the future.

If you go the module route you can add your own scripting functions but the classes your module uses won’t be in the right class loader to use the way you’re asking.

---

_[View the full topic](https://forum.inductiveautomation.com/t/adding-java-custom-classes-to-ignition/15202)._