Participating Frequently

Question

ColdFusion Builder 2018 and Big Sur - problems launching

Forum|Forum|5 years ago
November 17, 2020
5 replies
3906 views

Hi

Since upgrading to Big Sur on MacOS I have found that ColdFusion Builder 2018 will not start up fully.

Initially it quit before startup with java.lang.NullPointerException

---

!ENTRY org.eclipse.jdt.compiler.tool.nl_ja 2 0 2020-11-17 11:41:23.455
!MESSAGE Could not resolve module: org.eclipse.jdt.compiler.tool.nl_ja [451]
Unresolved requirement: Fragment-Host: org.eclipse.jdt.compiler.tool
Unresolved requirement: Fragment-Host: org.eclipse.jdt.compiler.tool

!ENTRY org.eclipse.osgi.compatibility.state.nl_ja 2 0 2020-11-17 11:41:23.455
!MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_ja [473]
Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state
Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state

!ENTRY org.eclipse.jdt.compiler.apt.nl_ja 2 0 2020-11-17 11:41:23.460
!MESSAGE Could not resolve module: org.eclipse.jdt.compiler.apt.nl_ja [450]
Unresolved requirement: Fragment-Host: org.eclipse.jdt.compiler.apt
Unresolved requirement: Fragment-Host: org.eclipse.jdt.compiler.apt

!ENTRY org.eclipse.osgi 4 0 2020-11-17 11:41:23.461
!MESSAGE Application error
!STACK 1
java.lang.NullPointerException

---

After restarting, it will launch and show the Launcher palette, but thereafter although the app launches and renders the menu bars, none of the palletes launch.

The menus are all functional and although a project won't launch it is possible to select a new project and force it to launch.

However it does not display all of the files tabs in the project and click in a file or its file tab causes files to partially appear/reappear.

There is sometimes a message about the start page other times not.

Completely unusable.

Any ideas? I've googled various keywords and phrases but don't find anything. The only difference in my setup is the recent change to Big Sur.

This topic has been closed for replies.

H

hansB87F

Participant

I had to backup my drive and did a factory reset. Reinstalled all my softwares and everything is running great. I have not clicked any update from Apple ever since November.

S

ServeLife

Participating Frequently

How to solve libjvm.dylib problem when installing CF Builder on MacOS Big Sur and MacOS Monterey for Intel and M1, M1 Pro and M1 Max Apple products

This stems from a lack of package content trust and the Eclipse being behind the curve:

For M1, M1 Max, M1 Pro Machines ensure that Rosetta is installed on your machine
Download a fresh copy of Eclipse from the main site 09-21 and install that first as the Eclipse wth CFBuilder is outdated and tired
Next download a fresh copy of CFBulder
Using ZSH Terminal CD to the location and run this command on that file
We are going to use the Xattr and quarantine the application to launch it - see this page https://eclecticlight.co/2017/12/11/an-introduction-to-extended-attributes-xattrs/
sudo xattr -d com.apple.quarantine ColdFusionBuilder_2018_WWEJ_osx10.dmg
This sets the file - now run the CFbuilder and perform attaching this to the new Eclipse
Enter in your license key up front as it is easier on this integration
Install CF 2018 and CF 2021 servers using the same commands above against these so they install
Launch Eclipse and look for the ColdFusion Perspective
Add in your servers
Voila you have 2 recent CF instances with a fresh powerful CF Builder in the newest Eclipse
I have installed CFBuilder this way on MacOS Monterey on both Intel Macs and M1 and M1 Pro Macs

S

ServeLife

Participating Frequently

Also to update 2018 from version 2 to most recent:

Use FireFox
Launch ColdFusion 2018 on FireFox
Server Updates --> Do Upgrade 4 first - on that tab - tab twice and the Download and Install buttons will show
After installing and restarting Upgrade 4 you can go all the way to the most recent version and install that cumulatively.

Good Luck - I have finally found solutions to move to MacOS Monterey using both these solutions and Ortus Solutions CommandBox with Docker MS SQL Server

Charlie Arehart

Community Expert

FWIW, Adobe has come out with a post today clarifying that while, for now, Big Sur is simply not supported for CF Builder, they are "working on making ColdFusion Builder to be compatible with Big Sur". That's encouraging, though it's not clear if that's about the current CFBuilder or the NEXT version (to be based on VSCode).

But if anyone has more specific questions on that, it would seem best to ask there on that post (if not also the bug report Dommie shared below, last week).

/Charlie (troubleshooter, carehart. org)

H

Hans5C99

Participant

Thanks for the update Charlie! I found a workaround to use CFBuilder while on a Mac. I have CFBuilder on a PC then on the Mac, I remote into.

Charlie Arehart

Community Expert

That's an interesting solution, Hans. Good "outside the box" thinking. But I do realize others may balk at the idea ("screw that noise", in coarser words).

That said, I'll note this for the sake of anyone who may be so desperate as to want to consider it: CFB does come with a 60-day free trial, so it may well be something to consider, if you DID have a spare PC (or Linux) machine around. You COULD certainly install that trial (remoting into it, if needed). And depending on the network config you could even point that CFB at CF (and perhaps your code) on your mac or a shared server.

At least it buys some time, in the hope that perhaps Adobe would address this issue with Big Sur before the trial's up. (And BTW, when a CFB trial ends, it doesn't "stop working". It turns into the free "Express" edition, with certain features removed--some of which are ones that many folks may never notice.)

Just sayin'. 🙂 And "please don't shoot the messenger".

/Charlie (troubleshooter, carehart. org)

Ali Sozkesen

Participating Frequently

I ask everyone viewing this message to vote & comment the related bug to make it come to an eye

https://tracker.adobe.com/#/view/CFB-4198463

Charlie Arehart

Community Expert

I don't have a solution, but some info that may be useful to some.

First, of course this challenge happens often with new OS builds (Mac or Windows, whether with CF or CFB). It's even worse with CFB and MacOS: the CF Builder System Requirements page does indicate that it supported only 10.13 (High Sierra)! And while there was an update 1 for it , that update did not indicate a change in OS support. 😞

That said, I realize everyone reading this may already understand that, and just want to identify any possible workarounds. I just wanted to share this, if it may be helpful to anyone. (I realize it doesn't solve the problem.)

Finally, FWIW, we can take some consolation in knowing that this sort of problem will diminish in time, as Adobe has announced that they are rebuilding CFBuilder 2021 to be based on vscode instead (either as a plugin or as a standalone packaging, just like they did with CFBuilder and how it was available either as an Eclipse plugin or as a standalone. Of course, current vscode users will far prefer the plugin route.)

Time will tell how it goes, if/how it's better than other vscode cfml extensions, etc. But it does seem that our hassles with CFBuilder as built on Eclipse will be going away in time. 🙂

Until then, if there are some workarounds to get CFB working on Big Sur, that will be great.

/Charlie (troubleshooter, carehart. org)

DommieAuthor

Participating Frequently

Hi Charlie

Thanks for the input. I have got well used to limping the various ColdFusion editors between MacOS and PC updates over the years!

Have to say I am surprised that CFBuilder 2018 seems to be such a dead end now, especially as I only upgraded last year.

Should they really still be selling the 2018 if its so OS version specific?

I'm pretty much done with Adobe's tools now there are some pretty decent alternatives, I don't see there's much ROI really

Charlie Arehart

Community Expert

While it's fair to assert that cfbuilder ON ECLIPSE seems a "dead end", as far as updates and updating for recent macos versions, it's NOT fair to say that about cfbuilder entirely when again Adobe is working on a new vs code variant.

And while some may argue "there are already vs code cfml plug-ins", cfbuilder does much more than the equivalent of such existing plugins--though far too many people never fully leverage cfb's features to appreciate that distinction.

Why does that happen? Human nature, lack of desire to read docs on the part of most, a relatively small population of cfb users to generate a segment of the community to share discoveries.

It's a sad state, yes. Dismal? No. Dead? No. Dying? I think we need to see the new version and its successors (the first version will not be complete, it seems). Will some choose not to wait? Sure. Heck, many left it long ago, or never tried. Some hated eclipse. Most never appreciated what cfb had to offer. Adobe will have a job winning folks back, but depending on how it goes, they may well be able to.

But it's not critical to cf's success. More a nice to have than a have to have, obviously. And since they give away cfb with every CF license purchased (1 for standard, 3 for enterprise), there's even less reason to hear much complaint. Some just ignore it.

But I do hope that a solution is found for this big sur problem (and I think it will be), and especially as you've paid for it I hope you may be able to fully leverage it--as I still have hope that more people will do that. It's not everyone's cup of tea, but it's far more capable--and worth exploring--than most seem to realize. There's definitely ROI for those who do. And I can even directly help any who doubt that, as I've been doing it for over a decade.

/Charlie (troubleshooter, carehart. org)