Include provided scoped dependencies in Flow maven plugin class scanning #21192
Labels
Comments
mshabarov
moved this from 🪵Product backlog
to 🅿️Parking lot
in Vaadin Flow ongoing work (Vaadin 10+)
|
I did a couple of tests, and it seems including provided dependencies seems not to break builds. |
mcollovati
added a commit
that referenced
this issue
Apr 9, 2025
Adds the "provided" scope to the list of Maven dependency scopes considered during class scanning by the Flow maven plugin. Fixes #21192
github-project-automation
bot
moved this from 🅿️Parking lot
to Done
in Vaadin Flow ongoing work (Vaadin 10+)
github-project-automation
bot
moved this from Maybe
to Done / Pending Release
in Vaadin Flow enhancements backlog (Vaadin 10+)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the Flow maven plugin ignores dependencies with provided scope during frontend class scanning, except for portlet and
javax.servletAPI artifacts.This filter comes probably from the initial plugin implementation and is most likely not required anymore.
Also, having artifacts in provided scope referencing frontend resources could potentially be a valid use case, for example if the dependency is not packaged with the application but provided at runtime.
The text was updated successfully, but these errors were encountered: