Forum Discussion

rpatrick00's avatar
rpatrick00
Contributor
5 years ago

Custom Snap Pack versioning is broken?

I have a custom snappack (version = 1, sl_build = 42) deployed in my organization’s shared folder that is in used by multiple projects. I have developed a completely rewritten version of the snappac...
ptaylor's avatar
ptaylor
Employee
5 years ago

Robert,

I’ve been testing this using a new snap pack created with our maven archetype.

I’ve been successfully able to update the version number and get the behavior you expect, where the new version just replaces the old one.

However, there are number of places where the version and build numbers need to match:

  1. The VERSION property in the <properties> section of the pom. You’ve changed this to 2.
  2. The sl_build property in the <properties> section. You’ve changed this to 1, correct?
  3. The <version> at the top of the pom should be VERSION-sl_build, so in your case 2_1.
  4. The VERSION in the config/directives file should be 2.
  5. The @Version annotations on all of the snaps and accounts should have snap = 2.

Can you please verify all of that?

  • ptaylor's avatar
    ptaylor
    Employee
    5 years ago

    Also, after uploading the new zip file, you need to refresh the Designer tab in your browser so that the catalog is reloaded. You’ll see the old version number if you don’t do that. I assume you refreshed.