That's an OK approach if there is a well-defined base of modules that several projects use. But that's really not the case.and other 3 extra specializations.the base would than have all common modules defined.so you could have "keycloak-base" feature pack that all other 3 extend.A feature-pack can extend another feature pack,I am sure you guys know that.
tomaz
--
On Tue, Jun 16, 2015 at 2:18 PM, Stan Silvert <ssilvert@redhat.com> wrote:
Cross-posting to wildfly-dev.
It sounds like we need a way to standardize module.xml definitions
across projects and have them accessible from maven GAV's. These
module.xml files are rarely different between projects and it doesn't
make sense for each feature pack to define its own copy.
On 6/15/2015 4:08 PM, Bill Burke wrote:
> Module definition is now done in 3 places? Copies of one another?
>
> eap6-service-overlay
> server-feature-pack
> adapter-feature-pack
>
> This is very very error prone guys. I guarantee somebody will forget to
> update something.
>
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev