# OpenCV Issue, The Ignition maven gateway archetype does not work for me with OpenCV

**URL:** <https://forum.inductiveautomation.com/t/opencv-issue-the-ignition-maven-gateway-archetype-does-not-work-for-me-with-opencv/64225>\
**Category:** Module Development\
**Created:** [September 19, 2022, 1:13pm UTC](https://forum.inductiveautomation.com/t/opencv-issue-the-ignition-maven-gateway-archetype-does-not-work-for-me-with-opencv/64225 "2022-09-19T13:13:37Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 19, 2022, 1:33pm UTC](https://forum.inductiveautomation.com/t/opencv-issue-the-ignition-maven-gateway-archetype-does-not-work-for-me-with-opencv/64225/2 "2022-09-19T13:33:49Z")

</div>

There are many hurdles to using OpenCV in Ignition, including the fact that its license is incompatible with inclusion in a module file. Consider using my [Image Streamer module](https://forum.inductiveautomation.com/t/automation-professionals-image-streamer-driver-module/29371/62), which works around that, and other issues, to load OpenCV classes and constants from its jar into Ignition’s scripting scope.

---

_[View the full topic](https://forum.inductiveautomation.com/t/opencv-issue-the-ignition-maven-gateway-archetype-does-not-work-for-me-with-opencv/64225)._