# .modl file structure

**URL:** <https://forum.inductiveautomation.com/t/modl-file-structure/68163>\
**Category:** Module Development\
**Created:** [January 3, 2023, 2:25pm UTC](https://forum.inductiveautomation.com/t/modl-file-structure/68163 "2023-01-03T14:25:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Denis\_Cote](https://avatars.discourse-cdn.com/v4/letter/d/ecb155/32.png) [@Denis\_Cote](https://forum.inductiveautomation.com/u/Denis_Cote)\
**Post date:** [January 3, 2023, 2:25pm UTC](https://forum.inductiveautomation.com/t/modl-file-structure/68163/1 "2023-01-03T14:25:21Z")

</div>

Is there a file structure we should stick to with the modl file? For example, where should 3rd party jar files live inside the modl file?

---

<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:** [January 3, 2023, 2:46pm UTC](https://forum.inductiveautomation.com/t/modl-file-structure/68163/2 "2023-01-03T14:46:35Z")

</div>

They should all be in the root of the zip. Each will need a callout in the `module.xml` to indicate what scope or scopes to load into. This is generally handled by declaring a dependency in the pom file.

Some luddites still use ant to build modules, so cannot be more specific. 😁