# Custom module will not start in Ignition Designer **URL:** \ **Category:** 3rd Party Modules\ **Created:** [June 8, 2016, 3:08pm UTC](https://forum.inductiveautomation.com/t/custom-module-will-not-start-in-ignition-designer/11789 "2016-06-08T15:08:35Z")\ **Posts on this page:** 12\ **Page:** 2
**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:** [June 27, 2016, 4:53pm UTC](https://forum.inductiveautomation.com/t/custom-module-will-not-start-in-ignition-designer/11789/21 "2016-06-27T16:53:51Z")
I don’t think it makes a difference in the end. I prefer each jar to be individually present instead of a single fat jar - it’s easier to see that your module is being packaged correctly at a glance that way. As for the issue with the palette - have you checked in the designer’s log console to see if anything relevant is being logged? Or launched with Java Console enabled to see if any errors get logged? ---
**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:** [June 27, 2016, 4:59pm UTC](https://forum.inductiveautomation.com/t/custom-module-will-not-start-in-ignition-designer/11789/22 "2016-06-27T16:59:24Z")
It would also be worth your time to get remote debugging setup: [docs.inductiveautomation.com/di … n+IntelliJ](https://docs.inductiveautomation.com/display/SE/Debugging+in+IntelliJ) ---
**Author:** ![cdulgar](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@cdulgar](https://forum.inductiveautomation.com/u/cdulgar)\ **Post date:** [June 27, 2016, 6:50pm UTC](https://forum.inductiveautomation.com/t/custom-module-will-not-start-in-ignition-designer/11789/23 "2016-06-27T18:50:32Z")
I notice the client and designer projects are packed into \*.pack.gz files. No need to do this with the 3rd-Party Dependency jar files I’ve been discussing? ---
**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:** [June 27, 2016, 7:08pm UTC](https://forum.inductiveautomation.com/t/custom-module-will-not-start-in-ignition-designer/11789/24 "2016-06-27T19:08:52Z")
You do need to pack any jar destined for client/designer scope. If the jar will be loaded into all 3 scopes, you’ll have 2 jars; one .pack.gz and another just a jar. edit: I can’t remember if it’s actually required or not… the gateway might pack any unpacked jars, resulting in a bit of an overhead when the client or designer first has to download the jars… but it might not be required. Just recommended. ---
**Author:** ![KathyApplebaum](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kathyapplebaum/32/7261_2.png) [@KathyApplebaum](https://forum.inductiveautomation.com/u/KathyApplebaum)\ **Post date:** [June 27, 2016, 7:52pm UTC](https://forum.inductiveautomation.com/t/custom-module-will-not-start-in-ignition-designer/11789/25 "2016-06-27T19:52:43Z")
It’s not required, but if you don’t pack it in advance the Gateway will pack it for you each time, leading to slower launch times for your designer and client. ---
**Author:** ![cdulgar](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@cdulgar](https://forum.inductiveautomation.com/u/cdulgar)\ **Post date:** [August 3, 2016, 4:14pm UTC](https://forum.inductiveautomation.com/t/custom-module-will-not-start-in-ignition-designer/11789/26 "2016-08-03T16:14:57Z")
I am back on this ‘Map Navigator’ trying to get it to work using Maven. The custom module compiles and installs without complaint. Yet, when I open an Ignition Designer Project expecting to see my new module in the Component Palette, I see the newly formed Group, but my module is not there. The Java Console displays this error when I load a project: * * * ## ERROR [main-Designer-Startup] Error starting up module mapnav Ignition Module java.lang.SecurityException: SHA-256 digest error for com/teamdev/jxmaps/swing/MapView.class My module project is named ‘mapnav’. The MapView.class is located inside one of TeamDev’s jar files. Is this an Ignition issue, or should I contact TeamDev? Attached are screen shots of: - The error in the Java Console - the MODL file contents - the Module.xml file contents ---
**Author:** ![cdulgar](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@cdulgar](https://forum.inductiveautomation.com/u/cdulgar)\ **Post date:** [August 3, 2016, 4:28pm UTC](https://forum.inductiveautomation.com/t/custom-module-will-not-start-in-ignition-designer/11789/27 "2016-08-03T16:28:14Z")
BTW, inside the Eclipse IDE, this project successfully runs as a Java Application. ---
**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 3, 2016, 4:29pm UTC](https://forum.inductiveautomation.com/t/custom-module-will-not-start-in-ignition-designer/11789/28 "2016-08-03T16:29:17Z")
I don’t think it’s anything to do with Ignition… are the jxmap jars signed? I’m guessing they’re signed - which is not compatible with being pack200’d. You may need to just remove the signature file from the jar. ---
**Author:** ![cdulgar](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@cdulgar](https://forum.inductiveautomation.com/u/cdulgar)\ **Post date:** [August 4, 2016, 4:46pm UTC](https://forum.inductiveautomation.com/t/custom-module-will-not-start-in-ignition-designer/11789/29 "2016-08-04T16:46:37Z")
Thanks for the response, Kevin. I’m forwarding your question to the TeamDev support people to see if they agree with this. ---
**Author:** ![cdulgar](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@cdulgar](https://forum.inductiveautomation.com/u/cdulgar)\ **Post date:** [August 5, 2016, 9:52pm UTC](https://forum.inductiveautomation.com/t/custom-module-will-not-start-in-ignition-designer/11789/30 "2016-08-05T21:52:18Z")
They guys at TeamDev gave the the “go ahead” to remove their signature files from the jar. This is the result: - mvn package - success - install ‘mapnav’ module into Ignition server - success - open an Ignition project - success (no errors): see DesignerStartup.png - display module in component palette - success - drag ‘mapnav’ component onto project main screen - success: see MapModuleScreenAdd.png - display ‘mapnamv’ component in designer screen - fail: see MapNavDesigner.png I small black graphic appears in the designer screen where I dropped the component. When I run the project, the component does not display on the screen. Do you know what this graphic indicates? We’re close. I can smell it! ---
**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 5, 2016, 10:10pm UTC](https://forum.inductiveautomation.com/t/custom-module-will-not-start-in-ignition-designer/11789/31 "2016-08-05T22:10:34Z")
It kind of looks like something that has 0x0 size and has resize handles all around it… ---
**Author:** ![cdulgar](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@cdulgar](https://forum.inductiveautomation.com/u/cdulgar)\ **Post date:** [August 10, 2016, 1:02pm UTC](https://forum.inductiveautomation.com/t/custom-module-will-not-start-in-ignition-designer/11789/32 "2016-08-10T13:02:30Z")
Up and running. Modified the component to inherit from AbstractVisionPanel (rather than ‘component’). [Previous page](https://forum.inductiveautomation.com/t/custom-module-will-not-start-in-ignition-designer/11789.md?page=1)