How does JMP's Add‑In "Check for updates when JMP starts" actually work?
I’m trying to understand how JMP handles add‑in updates. When installing an add‑in, there’s an option called "Check for updates when JMP starts." I assumed this meant JMP would detect a newer version of the same <STRONG>.jmpaddin</STRONG> file if I rebuilt it with a higher version number.
However, JMP never prompts for an update, even when the version in addin.def is incremented.
How is this feature supposed to work?
- Does JMP monitor a specific install folder?
- Does it remember the folder the add‑in was originally installed from?
- Is there a required setup for auto‑update detection?
I would appreciate clarification on the intended workflow
Basic Data Analysis and ModelingData AccessSharing and Communicating ResultsRe: How does JMP's Add‑In "Check for updates when JMP starts" actually work?I think Justin did explain this at some point of this presentation Scripters Club Recordings: Managing Your JMP Add-Ins (possibly Video 2)
Re: How does JMP's Add‑In "Check for updates when JMP starts" actually work?@jthi Yes, I believe I covered it there.
Basically, JMP is not using the version number to determine if there is a new version. It instead uses the last modification date of the .jmpaddin file where the add-in was installed from. If you are sharing the add-in with others, this works when users install add-ins directly from the shared location (and not a downloaded or copied file).
