I created a new blank ColdFusion project called “test1” and selected my CF 2016 server as it’s server.I have attempted several approaches at getting this working, here are the steps:įirst I will attempt to create a ColdFusion project within CFBuilder and then try to import my code into that project. ![]() ![]() I have installed the Subversive plugin into CFBuilder, which is what I previously used to use with Eclipse. I am using CF Builder 2016 and CF Server 2016 both installed on the same PC (a Windows PC) and installed them in their default locations (C:\ColdFusionBuilder2016 and C:\ColdFusion2016). You can also reach out to the CF Product Manager, Rakshith Naresh, who has offered his email address on various CF team blog posts: that’s helpful.I am having real issues trying to get SubVersion working smoothly with CFBuilder 2016. “Īnd then they reference that other link I just shared for the enterprise lifecycle policies, which adds still more information on obtaining such “extended support”. Extended Maintenance and Support provides the extra time you may need, to plan your migration to Adobe’s latest technology. This provides, five years of product support from the general availability date of a product.Įxtended support provides an additional two years of Platinum Maintenance and Support services after the end of Core Support. “ Core support is the time frame wherein the product and the support programs are available. Separately, the Adobe CF team offered an explanation in that 2017 post (which I link to in the first paragraph above) when CF10 support ended. Well, while that EOL matrix page itself does not offer an explanation, there is another page which does: What does “core support” mean versus “extended support”?Īs you view those columns, do note that there are two “support” dates, with one (“extended support”) that goes well beyond the other (“core support”). That’s the other reason I felt it valuable to create the table above, to make this info easier to consider, and to post it here in the community portal. Note that the result includes both products with coldfusion or 11 in their name (like ColdFusion 11.x) as well as also products with coldfusion in their name and 11 in their support dates, which is why you will see ColdFusion Builder 2.0, whose “general availability” date has 2011. That’s one reason I created the table above.Īnd while you can try to search for a specific version, such as: ![]() Which will find all CF versions listed, do note that the result is not in order (even within CF vs CF Builder). ![]() While of course you can use the page’s search feature, such as for: This information was obtained from the official Adobe “Products and technical support periods” page, and certainly that takes precedence over this (and while that page may be updated, there’s no guarantee that this blog post in the CF Community Portal will be updated when that page is.)īut do note that this official Adobe support matrix is for all Adobe products and historical version numbers (288 listed there as of this writing), and it shows only 25 at a time. (For the official location to find this information and see updates going forward, see additional discussion after the table.) Product nameįinding the official Adobe source of this information To help with assessing the state of the version you’re running or may be considering, here is a table of the past several versions of ColdFusion, and all versions of ColdFusion Builder. ColdFusion 10 support ended in May of 2017. For instance, note that as for CF, only CF11 and CF2016 are currently supported (being updated publicly, aka “core support”), as of this writing in January 2018. Have you wondered just when “support” (available updates) for a given CF or CF Builder version will (or did) end? This post tells you, for the past several CF releases, and all CF Builder releases, with some additional related information (like, “what’s ‘core support’ vs ‘extended support’?”)Įspecially as we enter 2018, and with a new ColdFusion release likely due out later this year (the prerelease is named Aether, and you can request to be considered for access to that), it’s time again for those running older CF versions to consider carefully the version they’re running.īut perhaps most important, it’s time for folks to pay attention to whether Adobe is (or is no longer) offering publicly available updates (bug fixes and security updates) for whatever version they run.
0 Comments
Leave a Reply. |