โ06-01-2017 10:07 AM
Hi,
Iโm deploying a new version of my snap pack and Iโd like to know what changes need to be made to the pom.xml to guarantee that a new version of a snap is picked up by SnapLogic.
Iโm playing around with the sl_build and VERSION numbers in the pom.xml. Iโve both seen new version of the snaps picked up and old snap versions execute if I just increment the sl_build number.
Can someone from the dev team confirm the guaranteed way of pushing an update to a Snap pack.
PS: Iโm using mvn clean install to build my snap and deploying via the SnapLogic GUI
โ06-14-2017 05:35 AM
Not on dev team, but what Iโve always done is:
That hasnโt worked? Where are you uploading the snap pack? Do you have multiple instances of your snap pack in your org?
โ06-14-2017 04:15 PM
This is what has worked for me everytime
mvn clean install -DskipTests -DVERSION=1 -Dsl_build=00XXX
Where sl_build is increment with every new build and the resultant package (zip file ) is uploaded to projects/shared and not into any individual shared space, refresh designer or login/logout.