Thanks koryknick - this might just be the simplistic genius i was looking for!
We use gmail if that helps.
This turned out to be user error on my part. The problem is that the new archetype generates a POM with the version number if two places: the normal Maven version tag and the sl_build property. I changed the version number in one place but not the other. Can we please make this version handling more Maven-like so that only needs to be changed in one place?
Can you say more specifically how exactly the version number is changing and how you’re redeploying it? Are you using “mvn snappack:deploy” to redeploy?
I have been changing the version number from 1-0001 to 1-0002, 1-0003, etc. and yes, I am “mvn clean install snappack:deploy” to redeploy.
I was accidentally using the Cloud Snaplex but when I switched back to my EC2-based snaplex, now I am getting a different error…
I finally just deleted the snappack, shutdown the snaplex, removed the directory created on the snapplex, restarted, and redeployed and things appear to be back to normal. Hoping that I don’t have to do that every time…
