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

project not working with latest flow change #23

Closed
Tracked by #7057
ZheSun88 opened this issue Dec 2, 2024 · 3 comments · Fixed by vaadin/flow#20601
Closed
Tracked by #7057

project not working with latest flow change #23

ZheSun88 opened this issue Dec 2, 2024 · 3 comments · Fixed by vaadin/flow#20601

Comments

@ZheSun88
Copy link
Contributor

ZheSun88 commented Dec 2, 2024

with the latest flow version.
i got this error from building the project.

Caused by: java.lang.NoSuchMethodError: 'org.reflections.util.ConfigurationBuilder org.reflections.util.ConfigurationBuilder.setExpandSuperTypes(boolean)'
    at com.vaadin.flow.server.scanner.ReflectionsClassFinder.<init> (ReflectionsClassFinder.java:66)
    at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0 (Native Method)
    at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance (NativeConstructorAccessorImpl.java:77)
    at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance (DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstanceWithCaller (Constructor.java:499)
    at java.lang.reflect.Constructor.newInstance (Constructor.java:480)
    at com.vaadin.flow.plugin.maven.Reflector.getOrCreateClassFinder (Reflector.java:211)
    at com.vaadin.flow.plugin.maven.Reflector.createMojo (Reflector.java:180)
    at com.vaadin.flow.plugin.maven.FlowModeAbstractMojo.execute (FlowModeAbstractMojo.java:284)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)

can be reproduced with

V24.5.7/F24.5.8
V24.6.0.beta1/F24.6.0.beta4(also beta5)

@mshabarov mshabarov added the bug Something isn't working label Dec 3, 2024
@mshabarov mshabarov moved this from 🟢Ready to Go to ⚒️ In progress in Vaadin Flow ongoing work (Vaadin 10+) Dec 3, 2024
mcollovati added a commit to vaadin/flow that referenced this issue Dec 3, 2024
The Flow Maven Plugin uses a class loader that combines project and plugin
dependencies to ensure class scanning happens on runtime artifacts.
However, plugin execution may fail if the project defines dependency versions
incompatible with those used by the plugin.

This change enforces the use of plugin-defined versions for certain
dependencies not directly used by Flow at runtime. Additionally, it logs
potential incompatibilities for other dependencies if the build fails.

Fixes vaadin/mpr-demo#23
@mshabarov mshabarov moved this from ⚒️ In progress to 🔎Iteration reviews in Vaadin Flow ongoing work (Vaadin 10+) Dec 3, 2024
mshabarov pushed a commit to vaadin/flow that referenced this issue Dec 3, 2024
…20601)

The Flow Maven Plugin uses a class loader that combines project and plugin
dependencies to ensure class scanning happens on runtime artifacts.
However, plugin execution may fail if the project defines dependency versions
incompatible with those used by the plugin.

This change enforces the use of plugin-defined versions for certain
dependencies not directly used by Flow at runtime. Additionally, it logs
potential incompatibilities for other dependencies if the build fails.

Fixes vaadin/mpr-demo#23
@github-project-automation github-project-automation bot moved this from 🔎Iteration reviews to Done in Vaadin Flow ongoing work (Vaadin 10+) Dec 3, 2024
vaadin-bot pushed a commit to vaadin/flow that referenced this issue Dec 3, 2024
…20601)

The Flow Maven Plugin uses a class loader that combines project and plugin
dependencies to ensure class scanning happens on runtime artifacts.
However, plugin execution may fail if the project defines dependency versions
incompatible with those used by the plugin.

This change enforces the use of plugin-defined versions for certain
dependencies not directly used by Flow at runtime. Additionally, it logs
potential incompatibilities for other dependencies if the build fails.

Fixes vaadin/mpr-demo#23
vaadin-bot pushed a commit to vaadin/flow that referenced this issue Dec 3, 2024
…20601)

The Flow Maven Plugin uses a class loader that combines project and plugin
dependencies to ensure class scanning happens on runtime artifacts.
However, plugin execution may fail if the project defines dependency versions
incompatible with those used by the plugin.

This change enforces the use of plugin-defined versions for certain
dependencies not directly used by Flow at runtime. Additionally, it logs
potential incompatibilities for other dependencies if the build fails.

Fixes vaadin/mpr-demo#23
vaadin-bot pushed a commit to vaadin/flow that referenced this issue Dec 3, 2024
…20601)

The Flow Maven Plugin uses a class loader that combines project and plugin
dependencies to ensure class scanning happens on runtime artifacts.
However, plugin execution may fail if the project defines dependency versions
incompatible with those used by the plugin.

This change enforces the use of plugin-defined versions for certain
dependencies not directly used by Flow at runtime. Additionally, it logs
potential incompatibilities for other dependencies if the build fails.

Fixes vaadin/mpr-demo#23
vaadin-bot added a commit to vaadin/flow that referenced this issue Dec 3, 2024
…20601) (#20605)

The Flow Maven Plugin uses a class loader that combines project and plugin
dependencies to ensure class scanning happens on runtime artifacts.
However, plugin execution may fail if the project defines dependency versions
incompatible with those used by the plugin.

This change enforces the use of plugin-defined versions for certain
dependencies not directly used by Flow at runtime. Additionally, it logs
potential incompatibilities for other dependencies if the build fails.

Fixes vaadin/mpr-demo#23

Co-authored-by: Marco Collovati <marco@vaadin.com>
vaadin-bot added a commit to vaadin/flow that referenced this issue Dec 3, 2024
…20601) (#20604)

The Flow Maven Plugin uses a class loader that combines project and plugin
dependencies to ensure class scanning happens on runtime artifacts.
However, plugin execution may fail if the project defines dependency versions
incompatible with those used by the plugin.

This change enforces the use of plugin-defined versions for certain
dependencies not directly used by Flow at runtime. Additionally, it logs
potential incompatibilities for other dependencies if the build fails.

Fixes vaadin/mpr-demo#23

Co-authored-by: Marco Collovati <marco@vaadin.com>
vaadin-bot added a commit to vaadin/flow that referenced this issue Dec 3, 2024
…20601) (#20606)

The Flow Maven Plugin uses a class loader that combines project and plugin
dependencies to ensure class scanning happens on runtime artifacts.
However, plugin execution may fail if the project defines dependency versions
incompatible with those used by the plugin.

This change enforces the use of plugin-defined versions for certain
dependencies not directly used by Flow at runtime. Additionally, it logs
potential incompatibilities for other dependencies if the build fails.

Fixes vaadin/mpr-demo#23

Co-authored-by: Marco Collovati <marco@vaadin.com>
@vaadin-bot
Copy link
Contributor

This ticket/PR has been released with Vaadin 24.6.0.beta3 and is also targeting the upcoming stable 24.6.0 version.

@vaadin-bot
Copy link
Contributor

This ticket/PR has been released with Vaadin 24.5.8.

@vaadin-bot
Copy link
Contributor

This ticket/PR has been released with Vaadin 24.4.21.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment