I am eagerly waiting for the following add-ons published in 6.10 version apart from few others are done! I shall upgrade my project after having those app-components are upgraded to ensure compatibility!
Thanks in advance.
Please be patient. Do not expect all free add-ons will be tested and upgraded next day after the new framework release.
Hi. I’m just curious about the protocol regarding add-ons. In general. For example, is the author (of the add-on) expected to maintain the add-ons? If so and an author decides to stop supporting the add-on, can (should) the consumer take on the risk of using the legacy add-on code? Are the supported versions listed in the marketplace those that are specified by the author or those vetted by the Cuba team? Perhaps these types of questions are covered in documentation somewhere. Any insight or direction is appreciated. Thanks.
Hi Keith,
The protocol is not fully established yet, but I can answer some of your questions with our current understanding.
is the author (of the add-on) expected to maintain the add-ons?
We can only promise that add-ons developed by Haulmont will be properly maintained. For other add-ons, we take no responsibility in quality, compatibility with future framework versions, etc.
If so and an author decides to stop supporting the add-on, can (should) the consumer take on the risk of using the legacy add-on code?
Even if author does not update the addon for a newer framework version, you can try to use it anyway - there is a good chance that it will work fine. For example, if your project is based on platform 6.10 and you want to use an addon that is built only for 6.9, add it to the project and ignore warnings from Studio. Gradle will use the newer dependencies - 6.10 in this case, which is what you need.
Also, most add-ons are open-source, so you can easily build them from sources locally and upgrade to the newer platform version.
Are the supported versions listed in the marketplace those that are specified by the author or those vetted by the Cuba team?
They are specified by the author. We only check that they really exist in repository and the add-on can be used in a project.
Thank you. That makes sense.
Hi, speaking of my forgot-password add-on, I need to find 2 to 4 spare hours because I have to change the login window for the new hover theme, and more importantly I need to remove my anonymous services support, now that the CUBA team has integrated it in the core.
So no, it’s not just a “bump the version” action, sorry 
P.
PS: regarding my anonymous services support, as you can imagine by what I’ve said before, I’m going to deprecate and remove it immediately, starting from the first version targeting 6.10. So if anyone is using it, you’ll need to move to the standard and equivalent CUBA functionality.
Hi, I’ve just updated the forgot-password and user-profile component for 6.10, and they are published on bintray.
Sorry for the long delay, I’ve been very busy lately.
Paolo