[
https://issues.jboss.org/browse/WFLY-12299?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFLY-12299:
-----------------------------------------
jfdenise yesterday Author Member
@bstansberry , now that I see these "mini aggregations" of web-server+feature,
it looks wrong. We are loosing some flexibility to make layers "simpler" to use.
Having to express web-server in some cases is not that difficult and makes sense.
For future layers definition it would create, as you noted, some un-necessary complexity.
This transactions layer should depend on elytron+ee (it needs it in order to set
use-transaction-setup-provider).
I would be ready to open another JIRA and update layers and doc with the removal of
web-server for all layers that don't 100% require a web-server.
If we keep the web-server dependency for jaxrs, we could possibly rename it to be
"jaxrs-server" that would be the aggregation, jaxrs layer would not depend on
web-server (for very exotic case). That would seem more homogeneous.
We would keep the rule that all layers identified to be used from user configuration
should be provisioned and runnable alone (even if they don't offer any valid
feature).
More fine grain dependency for galleon basic layers
---------------------------------------------------
Key: WFLY-12299
URL:
https://issues.jboss.org/browse/WFLY-12299
Project: WildFly
Issue Type: Enhancement
Components: Build System
Reporter: Jean Francois Denise
Assignee: Jean Francois Denise
Priority: Major
Having basic layers to only depend on the layers (and features) they do require will
offer more flexibility than depending on web-server layer.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)