-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support layer exclusion #78
Comments
@fabrii , thank-you. |
Something that I should have mentioned that will help you understand why a
layer is present. We have documentation for the latest WildFly version that
covers the rules WildFly Glow relies on to identify layers.
In this documentation:
https://docs.wildfly.org/wildfly-galleon-feature-packs/ you will find the
existing rules (generic description), all the supported galleon
feature-packs for a given WildFly version, and for each defined layer, the
actual rules that are in use.
For example, for datasources we can see: org.wildfly.rule.class
<https://docs.wildfly.org/wildfly-galleon-feature-packs/#glow.org.wildfly.rule.class>
=java.sql,javax.sql
This means that if a class from these 2 packages is referenced, then
datasources layer is added.
…On Mon, Jun 17, 2024 at 9:31 PM Fabricio Gregorio ***@***.***> wrote:
It would be nice to support layer exclusion on WildFly Glow CLI.
In certain cases, some layers are added because of classes that are
present (but not used) in dependencies.
For example, primefaces library adds the "jpa" layer while
infinispan-cdi-embedded-jakarta adds the "micrometer" layer.
More info: https://groups.google.com/g/wildfly/c/nhbrC82ZUlg
./wildfly-glow scan --provision=SERVER --add-ons=metrics examples/custom.war
Wildfly Glow is scanning...
context: bare-metal
enabled profile: none
config stability: community
galleon discovery
- feature-packs
org.wildfly:wildfly-galleon-pack:32.0.1.Final
- layers
ee-core-profile-server
microprofile-health
jaxrs
microprofile-rest-client
jsf
jpa
micrometer
metrics
microprofile-telemetry
./wildfly-glow scan --provision=SERVER --add-ons=metrics --exclude-archives-from-scan=primefaces-*.jar examples/custom.war
Wildfly Glow is scanning...
context: bare-metal
enabled profile: none
config stability: community
galleon discovery
- feature-packs
org.wildfly:wildfly-galleon-pack:32.0.1.Final
- layers
ee-core-profile-server
microprofile-health
jaxrs
microprofile-rest-client
jsf
datasources --> Notice that JPA is gone but now datasources is detected. I am 100% sure the 'datasource layer' is not used by my application, but I dont know which dependency is adding it
micrometer
metrics
microprofile-telemetry
./wildfly-glow scan --provision=SERVER --add-ons=metrics --exclude-archives-from-scan=primefaces-*.jar,infinispan-*.jar examples/custom.war
Wildfly Glow is scanning...
context: bare-metal
enabled profile: none
config stability: community
galleon discovery
- feature-packs
org.wildfly:wildfly-galleon-pack:32.0.1.Final
- layers
ee-core-profile-server
microprofile-health
jaxrs
microprofile-rest-client
jsf
datasources
metrics
microprofile-telemetry
Now micrometer is out.
—
Reply to this email directly, view it on GitHub
<#78>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7KEC7RYFN377M3O23Q3YDZH42QPAVCNFSM6AAAAABJOTNHD6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGM2TQMBZGYZTCNQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be nice to support layer exclusion on WildFly Glow CLI.
In certain cases, some layers are added because of classes that are present (but not used) in dependencies.
For example, primefaces library adds the "jpa" layer while infinispan-cdi-embedded-jakarta adds the "micrometer" layer.
More info: https://groups.google.com/g/wildfly/c/nhbrC82ZUlg
Now micrometer is out.
The text was updated successfully, but these errors were encountered: