# How to include a dependency JAR file in the Maven .modl build?

**URL:** <https://forum.inductiveautomation.com/t/how-to-include-a-dependency-jar-file-in-the-maven-modl-build/27631>\
**Category:** Module Development\
**Created:** [August 21, 2019, 1:07pm UTC](https://forum.inductiveautomation.com/t/how-to-include-a-dependency-jar-file-in-the-maven-modl-build/27631 "2019-08-21T13:07:10Z")\
**Posts on this page:** 1\
**Showing post:** 11

<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:** [August 22, 2019, 2:23pm UTC](https://forum.inductiveautomation.com/t/how-to-include-a-dependency-jar-file-in-the-maven-modl-build/27631/11 "2019-08-22T14:23:58Z")

</div>

> [@bruce.burton](#):
>
> The 3rd party jar file is named ‘sapjco3.jar’ and the included one is named ‘jco-3.0.jar’.

This should be a consequence of the artifact id you used when installing into the local repository.

I'm afraid you won't be able to stop it from using the "$artifactId-$version.jar" format, which if I remember correctly for this particular jar is a problem because it needs to be called "sapjco3.jar" for some dumb reason.

see [Ignition changes JAR file names artificially](http://forum.inductiveautomation.com/t/ignition-changes-jar-file-names-artificially/17241)

---

_[View the full topic](https://forum.inductiveautomation.com/t/how-to-include-a-dependency-jar-file-in-the-maven-modl-build/27631)._