Maybe you are right, though I wasn't talking about doing this for one single plugin that runs on one platform. I was carefully trying to start a conversation about making stuff more easy for (new?) devs around PMS to write plugins, maybe even encouraging people to use Groovy for plugin development in the first place? But as you answered my question, it probably doesn't pay off bloating PMS with Groovy. Maybe we (or I) can look into that library resource file approach you hinted about, maybe that's the way to go. BTW, is there any irc channel you are using?
But it's very good to hear that writing plugins with Groovy is ok and already happening in the first place. Unfortunately I didn't learn about PMSEncoder before this thread, it would've helped quite a lot figuring things out
Do you know if there's more Groovy goodness around?
What actually started this whole thing was me trying to figure out how to write plugins. With the great help of taconaut I got started and was able to produce something that runs. I also started to think about writing some instructions down for others in the same position. Then I started thinking about how to make things easy, and got bedazzled by Groovy. However, I didn't find any common wiki for PMS developers? If somebody could create one, for example to github, I volunteer to write something down about getting started with plugin development (with Groovy). Or I can just blog about it, but I think the info around PMS is already way too scattered. I would still want to make things easier for new devs, embedding Groovy was not the primary goal, and I apologize if I got the message wrong in the first place.