# No Maven achetype for 7.7.8 in Maven Nexus Repository **URL:** \ **Category:** Module Development\ **Created:** [August 23, 2018, 4:30pm UTC](https://forum.inductiveautomation.com/t/no-maven-achetype-for-7-7-8-in-maven-nexus-repository/19389 "2018-08-23T16:30:59Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![davide.tarquini](https://avatars.discourse-cdn.com/v4/letter/d/b3f665/32.png) [@davide.tarquini](https://forum.inductiveautomation.com/u/davide.tarquini)\ **Post date:** [August 23, 2018, 4:30pm UTC](https://forum.inductiveautomation.com/t/no-maven-achetype-for-7-7-8-in-maven-nexus-repository/19389/1 "2018-08-23T16:30:59Z")
Hi all, I’m developing a new module for ignition and I am creating a test project with maven archetype. The problem is that there is no artifact in the Nexus Repository for my version 7.7.8. The nearest are 7.7.5 and 7.8.0 Have I to use the SDK archive manually? ---
**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 23, 2018, 4:51pm UTC](https://forum.inductiveautomation.com/t/no-maven-achetype-for-7-7-8-in-maven-nexus-repository/19389/2 "2018-08-23T16:51:28Z")
You can just leave it linked to 7.7.5. The SDK dependencies just provide an API for you to compile against, they don’t get included in your module when you build it. We don’t generally make API changes in minor versions, so linking against the API for 7.7.5 should be just as good as 7.7.9 or any other 7.7 version. (Assuming you want to build a module to install in Ignition 7.7, of course) ---
**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:** [August 24, 2018, 12:15pm UTC](https://forum.inductiveautomation.com/t/no-maven-achetype-for-7-7-8-in-maven-nexus-repository/19389/3 "2018-08-24T12:15:23Z")
> [@Kevin.Herron](#): > > Assuming you want to build a module to install in Ignition 7.7, of course Or you want to build a module that'll install in 7.7, 7.8, and 7.9. (-: ---
**Author:** ![PRAMANJ](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pramanj/32/66935_2.png) [@PRAMANJ](https://forum.inductiveautomation.com/u/PRAMANJ)\ **Post date:** [August 24, 2018, 2:47pm UTC](https://forum.inductiveautomation.com/t/no-maven-achetype-for-7-7-8-in-maven-nexus-repository/19389/4 "2018-08-24T14:47:42Z")
Hopefully modules developed in 7.8.\* will be downward compatible as well and will work on lower versions as well (7.7._) and on lower versions like 7.6._ (not sure if older versions are still in use, perhaps all would have upgraded to at least 7.7). Of course much depends upon which libraries the module uses, and whether they are affected I guess. ---
**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:** [August 25, 2018, 12:42am UTC](https://forum.inductiveautomation.com/t/no-maven-achetype-for-7-7-8-in-maven-nexus-repository/19389/5 "2018-08-25T00:42:12Z")
> [@PRAMANJ](#): > > Hopefully modules developed in 7.8.\* will be downward compatible as well and will work on lower versions as well (7.7.) and on lower versions like 7.6. No. Not at all. The APIs are explicitly not declared compatible. Forward compatibility works on an interface-by-interface basis. Multiple API tolerance exists in v7.7.8, v7.8.3+, and v7.9.x. Basically the same versions that support the new signature model. ---
**Author:** ![PRAMANJ](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pramanj/32/66935_2.png) [@PRAMANJ](https://forum.inductiveautomation.com/u/PRAMANJ)\ **Post date:** [August 25, 2018, 3:48am UTC](https://forum.inductiveautomation.com/t/no-maven-achetype-for-7-7-8-in-maven-nexus-repository/19389/6 "2018-08-25T03:48:43Z")
So its safer to compile with version 7.7 to be upward compatible with 7.8, 7.9 etc? Or we need to have separate build for 7.7.\* and 7.8.\* ? Do customers still use older version such as 7.7 or they generally all upgrade to highner version? What is the least common denominator for versions in use? ---
**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:** [August 25, 2018, 11:34am UTC](https://forum.inductiveautomation.com/t/no-maven-achetype-for-7-7-8-in-maven-nexus-repository/19389/7 "2018-08-25T11:34:33Z")
Compile with 7.7 to support 7.7, and you might get lucky and also support later versions. Depending on whether you use an API that has changed. In minor cases, the incompatibility can be accommodated with reflection. Of my four public modules, one supports all three versions out of the box (Simulation Aids), two support all three with some help from reflection (NoteChart and Ethernet/IP Suite), and the remaining module (TS DB Cache) supports 7.7 and 7.8 in one branch, and 7.9 in another branch. I won’t know what’s possible with 8.0 until I get my hands on a beta.