# Vision Module Faulting on startup due to Other Module Loaded **URL:** \ **Category:** Module Development\ **Tags:** vision, ignition81\ **Created:** [September 26, 2024, 4:04pm UTC](https://forum.inductiveautomation.com/t/vision-module-faulting-on-startup-due-to-other-module-loaded/96504 "2024-09-26T16:04:49Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [September 26, 2024, 4:58pm UTC](https://forum.inductiveautomation.com/t/vision-module-faulting-on-startup-due-to-other-module-loaded/96504/7 "2024-09-26T16:58:51Z")
Not a Maven guy, so I can't help you exactly with _what_ to change, but _none_ of those should be there. Your .modl file should only contain your module's direct artifacts (your own -common, -client, -designer, , -gateway jars, plus third party dependencies your module relies on, if any). Nothing provided by Ignition should be there. Are you using an old version of the Maven module plugin? > [@Accessing java API within an own module from perspectives](https://forum.inductiveautomation.com/t/accessing-java-api-within-an-own-module-from-perspectives/93064/8): > > I found the issue. You are right, the transitive dependencies are bundled. I forgot about to change the version of the ignition-maven-plugin to version 1.2.0 after creating it with the archetype. I just checked, because I would update the version and create a PR. But there is already one: [Upgraded Archetype Dependency Versions by cmwarre · Pull Request #7 · inductiveautomation/ignition-sdk-archetypes · GitHub](https://github.com/inductiveautomation/ignition-sdk-archetypes/pull/7) Thanks a lot for testing it. --- _[View the full topic](https://forum.inductiveautomation.com/t/vision-module-faulting-on-startup-due-to-other-module-loaded/96504)._