Hello, Francis Martens (Exalate) , David Martin
You may download the Exalate for SNOW jar from within the docker image like this:
TAG=`wget -q https://registry.hub.docker.com/v1/repositories/idalko/snownode/tags -O - | sed -e 's/[][]//g' -e 's/"//g' -e 's/ //g' | tr '}' '\n' | awk -F: '{print $3}' | tail -n1`; docker run --name snownode -d idalko/snownode:$TAG ; docker cp snownode:/opt/snownode/install/lib/com.exalate.snownode-$TAG-sans-externalized.jar /tmp/ ; docker stop snownode && docker rm snownode
You may install the jar file into your maven repo:
mvn install:install-file \ -Dfile=/tmp/com.exalate.snownode-$TAG-sans-externalized.jar \ -DgroupId=com.exalate \ -DartifactId=snownode \ -Dversion=$TAG \ -Dpackaging=jar \ -DgeneratePom=true
So then the dependency
<dependency><groupId>com.exalate</groupId><artifactId>snownode</artifactId><version>5.2.5-rc1</version></dependency>
is resolvable.
Similarily, you may download other exalate dependencies from within the image:
-rw-r--r-- 1 root root 3791317 Oct 1 08:03 com.exalate.exalate-console-5.2.3.jar -rw-r--r-- 1 snow snow 303327 Oct 1 07:58 com.exalate.exalate-domain-5.2.3.jar -rw-r--r-- 1 root root 10114 Oct 1 07:58 com.exalate.exalate-domain-utils-5.2.3.jar -rw-r--r-- 1 root root 276 Oct 1 07:58 com.exalate.exalate-editor-5.2.3.jar -rw-r--r-- 1 snow snow 68629 Oct 1 07:59 com.exalate.exalate-errors_2.12-5.2.3.jar -rw-r--r-- 1 snow snow 11026 Oct 1 07:58 com.exalate.exalate-license-5.2.3.jar -rw-r--r-- 1 root root 144302 Oct 1 07:59 com.exalate.exalate-persistence-api_2.12-5.2.3.jar -rw-r--r-- 1 snow snow 1305974 Oct 1 08:00 com.exalate.exalate-persistence_2.12-5.2.3.jar -rw-r--r-- 1 snow snow 741858 Oct 1 08:01 com.exalate.exalate-play-controllers_2.12-5.2.3.jar -rw-r--r-- 1 root root 126815 Oct 1 07:59 com.exalate.exalate-processors_2.12-5.2.3.jar -rw-r--r-- 1 snow snow 3144631 Oct 1 08:00 com.exalate.exalate-replication_2.12-5.2.3.jar -rw-r--r-- 1 snow snow 356785 Oct 1 08:01 com.exalate.exalate-routes_2.12-5.2.3.jar -rw-r--r-- 1 root root 1085509 Oct 1 07:59 com.exalate.exalate-scala-domain_2.12-5.2.3.jar -rw-r--r-- 1 snow snow 81903 Oct 1 07:59 com.exalate.exalate-scala-utils_2.12-5.2.3.jar -rw-r--r-- 1 snow snow 44744 Oct 1 07:58 com.exalate.exalate-utils_2.12-5.2.3.jar -rw-r--r-- 1 root root 4479695 Oct 4 13:39 com.exalate.snownode-5.2.5-rc1-assets.jar -rw-r--r-- 1 root root 5104396 Oct 4 13:39 com.exalate.snownode-5.2.5-rc1-sans-externalized.jar
Please, let me know, if this helps.
Regards, Serhiy.
When we are working with Scripts on the docker side are the replica and entity IHubissue objects like in the scripts for JIra?
Yes - it is the same code base (on that level)
Is there a repo I can access using Maven that will expose the Groovy classes used with the Service now side of the connection as obviously there are methods and properties that are for that side of the connection.
it would seriously speed up development time if there is a JAR exposed like the Jira side that can enable all the auto completed and inspection of methods as trying to get junior staff to understand how it all works with out a good reference and real IDE devoted to the SN side is painful to say the least.