Skip to content
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

feat: support scanning configuration in maven plugin #21125

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

mcollovati
Copy link
Collaborator

Allows to fine tune scanning for frontend resources by defining inclusion and exclusion rules in the flow maven plugin configuration.

Fixes #21052

Copy link

github-actions bot commented Mar 14, 2025

Test Results

1 179 files  + 2  1 179 suites  +2   1h 13m 53s ⏱️ +10s
8 106 tests +21  8 049 ✅ +21  57 💤 ±0  0 ❌ ±0 
8 450 runs   -  3  8 385 ✅  -  2  65 💤  - 1  0 ❌ ±0 

Results for commit b747894. ± Comparison against base commit aa0b723.

♻️ This comment has been updated with latest results.

@mshabarov mshabarov self-requested a review March 17, 2025 12:34
Allows to fine tune scanning for frontend resources by defining
inclusion and exclusion rules in the flow maven plugin configuration.

Fixes #21052
@mcollovati mcollovati force-pushed the issues/21052-maven_plugin_configurable_class_scan branch from ca52664 to 816e583 Compare March 17, 2025 15:10
@vaadin-bot vaadin-bot added +0.1.0 and removed +1.0.0 labels Mar 17, 2025
@mcollovati
Copy link
Collaborator Author

Currently, frontend scanner configuration is applied only to the Reflector class in flow-maven-plugin.
I think there is no need to duplicate the feature in the flow-dev-bundle-plugin since it is only used internally by Vaadin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Configurable class scanning in Flow Maven plugin
2 participants