[ https://issues.jboss.org/browse/WFLY-7524?page=com.atlassian.jira.plugin.... ] Dennis Gesker commented on WFLY-7524: ------------------------------------- Thanks for taking a look at this ticket [Sanne Grinovero|https://issues.jboss.org/secure/ViewProfile.jspa?name=sannegrin...] I'm not sure I've done a project in the past couple years that didn't have some kind of spatial element to it so I'd love to see the dependencies in WildFly. But, it would be great if spatial was included in the feature pack even if it results in a larger war/ear -- so even it not included with the server. But, you are right and I can see where some might cringe at those parts/extras that are part of the Hibernate project being included by default. What typically been done in the past when a product that provides a standards compliant capability (JPA in this case) has a useful functionality beyond the standard? Or, put another way, I'll gladly go with the flow based on how this "kind" of thing has been resolved in the past. So my 1, 2, 3 of the options you presented would be: * We could simply include all missing dependencies into WildFly * We can enhance the feature packs which we release with each release of Hibernate ORM * We could have the hibernate-orm module depend on an optional "spatial extensions" module w/o including it, and publish the missing module as a drop-in feature pack to be downloaded separately I absolutely don't want to make any waves. And, I am grateful to even have attention on this item because I use these features/libs quite a bit. Thank you SO much for even considering WFLY-7523 and WFLY-7524 Dennis -- This message was sent by Atlassian JIRA (v7.5.0#75005)