Exactly. Databinding consists of many plugin bundles.
Currently we have a rule that each plugin needs to be generified atomically. This means all the work needs to be done in one giant sprint by a single contributor, which creates an enormous workload for whoever does it. You need a volunteer willing to spend about a week of full-time work in order to convert one of these plugins -- and they need to do it all in one go or their giant change won't merge.
As it is, the workload is almost impossible. That's why nobody did it for about 10 years... but in 4.6 we managed to get it done for several databinding plugins.
If we want the work done faster, sprigogin's suggestion would be the way to go. Making the atomic unit for generification smaller would mean that someone could write a useful patch over a weekend rather than needing to do it as their day job for a week. That would mean more warnings in the short-term but also more people willing to help out.
You seem to be suggesting that you want to make the atomic unit for generification even larger than a single plugin. If we were to adopt that policy, the consequence would be that nobody will ever do the work. The plugins would never get generified. If it took 10 years to find somebody to do the work to convert 3 of the plugins, how long do you think it would take to find someone to convert - say - 10 of them in one go?
- Stefan
There is no such thing as databinding bundle. Databinding is a framework, different parts of which are implemented by separate plugins. According to official Eclipse policy minimal generification unit is a plugin. I personally think that generification would go faster if it were allowed to proceed on file-by-file basis, how it was successfully done for CDT a while ago.
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev