# 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:** 6

<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:** [September 4, 2017, 3:42pm UTC](https://forum.inductiveautomation.com/t/adding-java-custom-classes-to-ignition/15202/6 "2017-09-04T15:42:06Z")

</div>

Ah, in order for client/designer scoped jars to get loaded you have to run the pack200 tool on the jar first. You’ll notice those directories are full of jar.pack.gz files - these are packed jars.

If you want to use the jar in all scopes, then the easiest approach is to put both a packed and unpacked copy of the jar into the lib/core/common folder.

---

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