I want to create a trivial maven plugin with a mojo that does just one small function. I could create a repo just for that, with a repo name and artifactId to match. Or I could give it a more generic name / artifactId and if we need other things like my mojo we could just add them.

WDYT?

In general I don't like grab-bag projects and I'd oppose adding anything complex or likely at all to need much maintenance into any shared project. We used to have the licenses plugin mixed in a project with something else, and we're better off with it in its own project. But my thing will likely be maybe 10 lines of non-boilerplate code. It's that kind of thing I'm thinking about.

Writing this, I'm convincing myself I should start with a single-purpose thing and if there's every a concrete use case for some other similar thing we can fork it and create a new repo.


--
Brian Stansberry
Collaborative Partner - IBM
Architect, JBoss EAP
WildFly Project Lead
He/Him/His