Enable running npm project without maven

[caalador]

Enable generation and copying of all
required files without the need to execute maven.

Note! to run in npm mode without maven
the file src/main/resources/META-INF/VAADIN/config/flow-build-info.json
with the content { "compatibilityMode": false } needs to exist in the project.

Fixes #5927

---

This change is 

[denis-anisimov]

Reviewed 11 of 12 files at r1, 1 of 1 files at r3.
Reviewable status: 2 unresolved discussions, 0 of 1 LGTMs obtained (waiting on @denis-anisimov)

a discussion (no related file):

Note! to run in npm mode without maven
the file src/main/resources/META-INF/VAADIN/config/flow-build-info.json
with the content { "compatibilityMode": false } needs to exist in the project.

May I just set a property to run it in npm ?

---

---

flow-server/src/main/java/com/vaadin/flow/server/startup/DevModeInitializer.java, line 217 at r3 (raw file):

copyFrontendFilesFromJar

from Jars (plural) ?

Only jars ?
No need to care about compiled classes ? (e.g. classes folder)

[caalador]

Reviewable status: 2 unresolved discussions, 0 of 1 LGTMs obtained (waiting on @denis-anisimov)

a discussion (no related file):

Previously, denis-anisimov (Denis) wrote…

Note! to run in npm mode without maven
the file src/main/resources/META-INF/VAADIN/config/flow-build-info.json
with the content { "compatibilityMode": false } needs to exist in the project.

May I just set a property to run it in npm ?

You may just set it as a property, but in this case it becomes a question that where would you put it?
This is one solution that can be pushed to the version-control system and will therfore always work.
Having it in maven won't work as we don't in this case run maven.

You could create a servlet with the property as a servlet parameter, but as we generally don't need those...
Also it should work having it in application.property for spring projects, but the file recommendation is so that we could have all starters work the same way.

---

---

flow-server/src/main/java/com/vaadin/flow/server/startup/DevModeInitializer.java, line 217 at r3 (raw file):

Previously, denis-anisimov (Denis) wrote…

copyFrontendFilesFromJar

from Jars (plural) ?

Only jars ?
No need to care about compiled classes ? (e.g. classes folder)

Done.

[caalador]

Reviewable status: 2 unresolved discussions, 0 of 1 LGTMs obtained (waiting on @denis-anisimov)

---

flow-server/src/main/java/com/vaadin/flow/server/startup/DevModeInitializer.java, line 217 at r3 (raw file):

Previously, caalador wrote…

Done.

Also yes we only copy .js and .css files from the jar files so that they are available for webpack.

[vaadin-bot]

SonarQube analysis reported 1 issue

Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

1. JarContentsManager.java#L124: Return an empty array instead of null.

[denis-anisimov]

I'm fine with this.

Reviewed 1 of 1 files at r4.
Reviewable status: complete! all discussions resolved, 1 of 1 LGTMs obtained

a discussion (no related file):

Previously, caalador wrote…

You may just set it as a property, but in this case it becomes a question that where would you put it?
This is one solution that can be pushed to the version-control system and will therfore always work.
Having it in maven won't work as we don't in this case run maven.

You could create a servlet with the property as a servlet parameter, but as we generally don't need those...
Also it should work having it in application.property for spring projects, but the file recommendation is so that we could have all starters work the same way.

I'm just asking whether I may avoid flow-build-info.json modification but just set a property when I run a project.
Without any other context.

Normally I'm not aware about flow-build-info.json at all (sure, it's easier for us if we want to store it in VCS).
But I know that there is a property which I may use to enable npm (that's the only thing I need : to be able to run project in npm mode instead of bower since by default it's bower mode and I have to do something to start it in npm).

So if I may use a property without knowing anything about flow-build-info.json that's OK for me.

---