-
Close Search
Newbie
Clarification on the updating of packages in ColdFusion 2025.
Maybe I missed it in the documentation somewhere, but are ColdFusion 2025’s packages automatically updated when you install an update/hotfix? I thought we had to manually update them post-hotfix, either via ColdFusion Administrator or the CFPM utility?
Today I updated my ColdFusion 2025 server (fresh install with 0 updates installed) straight to Update 4 (since they’re cumulative). Here’s the process that I followed:
- Downloaded the Update 4 hotfix .jar and placed it on my server.
- Downloaded the Update 4 packages .zip and extracted it to my server.
- Updated “packagesurl” path in neo_updates.xml to point to the extracted packages .zip.
- Restarted ColdFusion services so ColdFusion picked up the “packagesurl” change.
- Stopped ColdFusion services.
- Installed the Update 4 hotfix via administrative command line, with administrator rights, and by using the JRE that comes with ColdFusion (and not any other JRE version).
- Checked to ensure ColdFusion had been restarted and the hotfix installed successfully.
I then logged into ColdFusion Administrator expecting to have to manually toggle to the latest package versions for the many packages that have been updated since ColdFusion 2025 released, but to my surprise it seems like they all had been “updated” to their latest versions.
Did I just miss that in the documentation, does the hotfix update also update packages?
Maybe I missed it in the documentation somewhere, but are ColdFusion 2025’s packages automatically updated when you install an update/hotfix? I thought we had to manually update them post-hotfix, either via ColdFusion Administrator or the CFPM utility?
Today I updated my ColdFusion 2025 server (fresh install with 0 updates installed) straight to Update 4 (since they’re cumulative). Here’s the process that I followed:
- Downloaded the Update 4 hotfix .jar and placed it on my server.
- Downloaded the Update 4 packages .zip and extracted it to my server.
- Updated “packagesurl” path in neo_updates.xml to point to the extracted packages .zip.
- Restarted ColdFusion services so ColdFusion picked up the “packagesurl” change.
- Stopped ColdFusion services.
- Installed the Update 4 hotfix via administrative command line, with administrator rights, and by using the JRE that comes with ColdFusion (and not any other JRE version).
- Checked to ensure ColdFusion had been restarted and the hotfix installed successfully.
I then logged into ColdFusion Administrator expecting to have to manually toggle to the latest package versions for the many packages that have been updated since ColdFusion 2025 released, but to my surprise it seems like they all had been “updated” to their latest versions.
Did I just miss that in the documentation, does the hotfix update also update packages?
You must be logged in to post a comment.
- Most Recent
- Most Relevant
This is not a change in behavior in cf2025. It’s how it worked as well for cf2023 and cf2021–which is when “packages” were introduced to cf.
Perhaps you came from running on cf2018? BTW, all those steps are only needed if your cf instance can’t access the internet; otherwise, you could have just run the update from the admin.
Finally, do beware that you need to change that packagesurl value before any subsequent update. If you look in the cf admin, you’ll see your value on the page shown via the “settings” tab at the top of the package management page. It also offers a button to revert it to the default, which is a url that obtains the package updates from Adobe’s servers.
