On Wed, Aug 22, 2018 at 5:53 AM, Chris McGee <[email protected]> wrote:
> I’ll give it some thought as to whether we want to continue to use the > abandoned code formatter or rely on developer diligence to keep the code > base formatted correctly. > The point is that odds are very high that whatever is making this plugin incompatible is most likely some little bit of meta data. The code is the code, NB Platform, in general, is more stable than not. Even a developer new to the platform could probably build this add on, tweak it to make it compatible, and bring it up to date quite quickly. I mean, who knows, right? Maybe, maybe not. Were someone on your team to do that, and submit the patch back to the original developer, then, tada the module is now "maintained". For maybe a couple hours work, until the next release of NB. Considering the time savings and other value you gain from using this plugin, don't you think it might be worth an hour or two to at least have someone take a serious look at it? Check it out, build it, take a look at it. If you have problems, folks here may be able to give detailed tips on getting the plugin to work again. They can readily help with the NB parts. The eclipse part, not so much, right? And this is likely a NB issue, not an eclipse formatter thing. AT WORST, you have a fork of this module now working for you, and you have an internal website somewhere hosting the fork artifact so it's available to your users as a module (this entails an XML file and your module, it's no big deal). Not the most egregious burden. Ideally, the author will incorporate your change and its now "up to date", just as it always has been. So, in total, the ask here isn't that great. What do you think? Regards, Will Hartung
