For some of the add-ons we use, they might have a Vaadin8 version, but not have a Vaadin7 compatibility version. What is the best practice in this case, have people found?
- Somehow find V7 branch of source code, and clone it
- Run migration tool on V7 cloned project, install to “local” repository ( my .m2 folder short term, my maven repository long term )
- Add local repository to my project so I can access new V7 migration add-on
Simplistic question, but is that how people have tended to handle this?
Also, in my case, 2 of my add-ons have V7 branches, and so are easy to clone. But 2 of my add-ons do not. How have people been solving that? This is more of a GIT question, I guess, but I am sure people have had this problem, so thought I would ask.
These are my add-ons that are impacted by this compatibility mode question, in case people are curious. I currently have requests to the developers to make sure I am not missing something someplace:
- [de.steinwedel.vaadin.addon:messagebox]
(https://vaadin.com/directory/component/messagebox) … 3.0.19 → 4.0.21 - [org.vaadin.addons:vaadin-excel-exporter]
(https://vaadin.com/directory/component/excel-exporter) … 1.0.8 → 2.0 - [tm.kod:numberfield7]
(https://vaadin.com/directory/component/numberfield7---numberfield7-add-on) … 0.0.4 → 0.0.5 - [org.vaadin.addons:exporter]
(https://vaadin.com/directory/component/exporter) … 1.0.0 → org.vaadin.haijian:exporter 2.0.2