Thanks. I went with a single mojo repo.
On Thu, Jun 18, 2026 at 5:22 PM Eduardo Martins <emartins(a)redhat.com> wrote:
Every time | saw someone doing a multi project repo, later the
author/team
regretted :-)
—E
On 18 Jun 2026, at 20:14, Brian Stansberry via wildfly-dev <
wildfly-dev(a)lists.jboss.org> wrote:
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
_______________________________________________
wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
Privacy Statement:
https://www.redhat.com/en/about/privacy-policy
List Archives:
https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...
--
Brian Stansberry
Collaborative Partner - IBM
Architect, JBoss EAP
WildFly Project Lead
He/Him/His