# Ignition Maven Plugin v1.0.11 Fails

**URL:** <https://forum.inductiveautomation.com/t/ignition-maven-plugin-v1-0-11-fails/12107>\
**Category:** Module Development\
**Created:** [September 8, 2016, 1:16pm UTC](https://forum.inductiveautomation.com/t/ignition-maven-plugin-v1-0-11-fails/12107 "2016-09-08T13:16:40Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![xasga](https://avatars.discourse-cdn.com/v4/letter/x/838e76/32.png) [@xasga](https://forum.inductiveautomation.com/u/xasga)\
**Post date:** [September 8, 2016, 6:21pm UTC](https://forum.inductiveautomation.com/t/ignition-maven-plugin-v1-0-11-fails/12107/3 "2016-09-08T18:21:00Z")

</div>

> [@Kevin.Herron](#):
>
> Hi, I'm not able to replicate issue #1 on any of the SDK example projects so I might need to see more of what you've got set up.

What info do you need me to provide?

> [@Kevin.Herron](#):
>
> #2 is because your gateway is not in "developer mode", which is a feature of the license you're running. I think you have to contact a sales rep to get a developer license these days (it's free). Alternatively... you can start the Ignition gateway with the system property "-Dia.developer.moduleupload=true" and it should allow modules to be loaded as well. You would add this to the additional params section in ignition.conf.

I installed a license that put the gateway in developer mode.  
This is what I saw as I installed the module manually:  
\<\<\<  
This module is not signed. You are currently running in developer mode and can run unsigned modules. Modules can make changes to your system. Be sure you understand the risk.

> > >

---

_[View the full topic](https://forum.inductiveautomation.com/t/ignition-maven-plugin-v1-0-11-fails/12107)._