Lucee 6.2 / 7.0 latest upgrades not showing in the admin workaround

Since 6.2 and 7.0 Lucee retrieves the list of available updates from maven, rather than from the Lucee update server.

Due to a hosting change with maven, we had to modify this process, as newer versions since 6.2.2.64-SNAPSHOT and 7.0.0.275-SNAPSHOT no longer show up as upgrade options from older versions of Lucee.

This is only a problem when trying to upgrade via the admin, if you are upgrading via changing the base docker images, this is not a problem.

The fix in is place since 7.0.0.303-SNAPSHOT / 6.2.2.82-SNAPSHOT

The workaround is to use the fallback s3 update mechanism via the admin, or do drop the latest snapshot / rc / stable into the /deploy folder

To access the s3 update mechanism, simply append old to the url for the updates page in the admin, i.e action=services.update to action=services.updateold

http://localhost:8888/lucee/admin/index.cfm?action=services.updateold

You will only need to do this once.

To verify this afterwards, simply compare what is listed on the download page with the versions list shown in the normal admin update page.

2 Likes

When I enter action=services.updateold, I don’t see any updates.
There’s an empty box where I should enter a custom update provider, but which one is it?

Ok. It works.
There are no stable releases, but I see the new RC and Snapshot

2 Likes

I’ve added a link to this to the breaking changes document for 6.2

2 Likes