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

flow server does not compile with JDKs 14GA, 15EA and 16EA #8661

Closed
manolo opened this issue Jun 30, 2020 · 3 comments · Fixed by #10497
Closed

flow server does not compile with JDKs 14GA, 15EA and 16EA #8661

manolo opened this issue Jun 30, 2020 · 3 comments · Fixed by #10497

Comments

@manolo
Copy link
Member

manolo commented Jun 30, 2020

Download a JDK version bigger than java 8. For instance, links for mac are:
java 9
java 10
java 15
java 17

Execute compilation and test of the two main modules in flow:

curl -o java.tar.gz appropriate_URL_for_the_JDK.tar.gz

rm -rf jdk*
tar xzf java.tar.gz

export JAVA_HOME=$PWD/jdk-*/Contents/Home
export PATH=$JAVA_HOME/bin:$PATH

rm -rf flow
git clone git@github.com:vaadin/flow.git

cd flow
mvn clean test -pl flow-server,flow-client

It fails with the error

ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project flow-server: Compilation failure
[ERROR] ./flow/flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java:[115,18] cannot access com.sun.beans.introspect.PropertyInfo
[ERROR]   class file for com.sun.beans.introspect.PropertyInfo not found
[ERROR]
@manolo manolo changed the title flow server does not compile with JDK-15 early access flow server does not compile with JDKs 14GA, 15EA and 16EA Jun 30, 2020
@pleku pleku added this to Needs triage in OLD Vaadin Flow bugs & maintenance (Vaadin 10+) via automation Aug 10, 2020
@pleku pleku moved this from Needs triage to Internal Backlog / Technical Debt in OLD Vaadin Flow bugs & maintenance (Vaadin 10+) Aug 10, 2020
@pleku
Copy link
Contributor

pleku commented Mar 26, 2021

@manolo is still issue still valid ?

@manolo
Copy link
Member Author

manolo commented Mar 29, 2021

will take a look

@manolo
Copy link
Member Author

manolo commented Mar 30, 2021

The problem is that it's necessary to set the ${maven.compiler.release} appropriately, there is a profile that automatically set it, but it's only activated in the case of java-11

OLD Vaadin Flow bugs & maintenance (Vaadin 10+) automation moved this from Internal Backlog / Technical Debt to Closed Mar 30, 2021
mshabarov pushed a commit that referenced this issue Mar 30, 2021
…10497) (#10501)

Fixes: #8661

Co-authored-by: Manuel Carrasco Moñino <manolo@vaadin.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

3 participants