Changes in Maven Coordinates or Maven Repos?

Module Development
1

HI,

I had a previously working build for an Ignition 8.1 plugin.

I’m currently trying to get that to work again. Also am I trying to progress my experiment more towards a final version of the plugin.

I am facing two issues:

  • The examples all refer to SNAPSHOT versions of the SDK libraries. This is fine during development, however referring to SNAPSHOT libs is not allowed (without jumping some hoops) in a Maven release. So I would like to refer to release versions instead.
  • I don’t seem to be able to refer to the previously existing 8.1.0-SNAPSHOT lib versions.

I already switched to the new repo urls. It also seems as if it is possible to get 8.3.0-SNAPSHOT versions for the libs, however the structure of the artifacts seems to have changed and I can’t seem to be able to resolve new versions of the 8.1 artifacts.

Is there a guide to how to migrate the dependencies from 8.1 to 8.3?

Do I need an account/login to be able to pull in released versions?

Chris

2

This is a good first step for seeing the changes in resource naming and paths.

3

Thanks for that … I think I even wen’t through it before.

Admittedly I would currently like to start with a plugin for 8.1 and add support for 8.3 later. Is it possible to pull the maven release-artifacts from the IA nexus? Do I need an account for accessing them? It seems the SNAPSHOT artifacts are publicly available, however the release versions aren’t.

4

Normally the module would be built separately for both versions, with the 8.3 module having upgrade methods that convert from the legacy 8.1 internal database record store to the new file based record store and similar needs.

I am interested why your 8.1 doesn't work as it did before, most of mine have worked fine since I wrote them.

5

Solved the issue … so I’ve successfully managed to pull in the dependencies for 8.1 and in a separate module for 8.3. Admittedly looking at the changes (which are generally not really existent) … I assume it was a Maven dependency resolution hickupp on my side here.

1 Like