Ignition 8.3 Maven / Sonatype Repo artifact missing

Module Development
1

I’m trying to get my module building under Gradle, it is complaining about a “ignition-laf:3.1.0-beta13” artifact that it can’t find:

> Could not find com.inductiveautomation.plaf:ignition-laf:3.1.0-beta13.
  Searched in the following locations:
    - https://maven.seeq-labs.com:9443/repository/inductive-automation-releases/com/inductiveautomation/plaf/ignition-laf/3.1.0-beta13/ignition-laf-3.1.0-beta13.pom
  Required by:
      project :ignition:sqim-v83:sqim-v83-client > com.inductiveautomation.ignitionsdk:client-api:8.3.0 > com.inductiveautomation.ignition:client-api:8.3.0

We use a mirror (https://maven.seeq-labs.com:9443) but it is configured to pull through from https://nexus.inductiveautomation.com/.

I tried to see if I could view the artifact on https://nexus.inductiveautomation.com/ but seems like you need a login to browse the artifacts.

Can anyone on the Inductive side confirm if com.inductiveautomation.plaf:ignition-laf:3.1.0-beta13 is there?

2

Make sure you are proxying these repos: ignition-sdk-examples/vision-component/pom.xml at f9aa673775043d4dafb0eddcc77981645528a2a2 · inductiveautomation/ignition-sdk-examples · GitHub

3

We do, but that artifact is missing from inductiveautomation-releases. If you look at the maven-metadata.xml file, the last version published there is 3.1.0-beta8. But Ignition 8.3 has a dependency on 3.1.0-beta13.

Edit: Ah, for some reason the new version has been published to inductiveautomation-thirdparty instead. Was this intentional? To speed up dependency resolution, we have a filter that assumes that all “com.inductiveautomation” artifacts come from the inductiveautomation-releases repository. This seems to be the only exception. We can remove the filter of course, but maybe you can fix this on your end, since this looks like an odd outlier?

4

ignition-laf is a weird edge case for us, because it's an artifact we get from a third party...but it's bespoke to us. Uploading it is a manual process and I'm fully guilty of putting it into different places in the past, but was told that thirdparty is the "more correct" location for it by one of our build engineers.

5

Gotcha, we’ll remove the filter on our end then. We added it to work around for Inductiveautomation-thirdparty should return 404 for missing files - #12, but that’s been fixed since.

1 Like