This may be more of a general maven question, but I have a question about exclusion management in our POMs: Where do the exclusions need to be listed? For my parts of the system, I have an inconsistent mix of declaring the exclusions in, say, boms/, ee-feature-pack/, and my individual extension modules. That seems like overkill, though, and is certainly not dry. Is it enough to declare the exclusions in the dependencyManagement section of the BOM, then just declare the (versionless) dependency in the other Maven modules that might need it? I don't want to repeat that large block of XML over and over, but I know we also don't want to ship any jars that we don't explicitly want. Jason Lee Principal Software Engineer Red Hat JBoss EAP _______________________________________________ wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

There might be some odd exception cases that I'm not thinking of, but IMHO exclusions should go in dependencyManagement. The proliferation of exclusions throughout our poms is one of the ugly points that we started to clean up in the big-bang. On Fri, Nov 11, 2022 at 9:21 AM Jason Lee <jasondlee(a)redhat.com&gt; wrote: > This may be more of a general maven question, but I have a question about > exclusion management in our POMs: Where do the exclusions need to be > listed? For my parts of the system, I have an inconsistent mix of declaring > the exclusions in, say, boms/, ee-feature-pack/, and my individual > extension modules. That seems like overkill, though, and is certainly not > dry. Is it enough to declare the exclusions in the dependencyManagement > section of the BOM, then just declare the (versionless) dependency in the > other Maven modules that might need it? > > I don't want to repeat that large block of XML over and over, but I know > we also don't want to ship any jars that we don't explicitly want. > > Jason Lee > > Principal Software Engineer > > Red Hat JBoss EAP > > _______________________________________________ > wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org > To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s -- Brian Stansberry Principal Architect, Red Hat JBoss EAP 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 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s