vaadin / skeleton-starter-flow Goto Github PK

View Code? Open in Web Editor NEW

31.0 37.0 33.0 9.22 MB

Default project template for Vaadin

Home Page: https://vaadin.com/start

License: The Unlicense

Java 83.84% CSS 8.07% HTML 8.09%

java web webcomponents getting-started project-templates vaadin

skeleton-starter-flow's Introduction

Skeleton Starter for Vaadin

This project can be used as a starting point to create your own Vaadin application. It has the necessary dependencies and files to help you get started.

The best way to use it is via vaadin.com/start - you can get only the necessary parts and choose the package naming you want to use. There is also a getting started tutorial based on this project.

To access it directly from github, clone the repository and import the project to the IDE of your choice as a Maven project. You need to have Java 8 or 11 installed.

Run using mvn jetty:run and open http://localhost:8080 in the browser.

If you want to run your app locally in the production mode, run mvn jetty:run -Pproduction.

Running Integration Tests

Integration tests are implemented using Vaadin TestBench. The tests take a few minutes to run and are therefore included in a separate Maven profile. We recommend running tests with a production build to minimize the chance of development time toolchains affecting test stability. To run the tests using Google Chrome, execute

mvn verify -Pit,production

and make sure you have a valid TestBench license installed (you can obtain a trial license from the trial page).

Project structure

The project follow Maven's standard directory layout structure:

Under the srs/main/java are located Application sources
- AppShell.java configures the @PWA annotation making the application installable
- GreetService.java is a service class
- MainView.java is an example Vaadin view
Under the srs/test are located the TestBench test files
src/main/resources contains configuration files and static resources
The frontend directory in the root folder contains client-side dependencies and resource files. Example CSS styles used by the application are located under frontend/themes

Workspace.xml file

IntelliJ IDEA uses workspace.xml file to cache user-specific project configuration. Tracking of local changes to the workspace.xml file can be prevented with the git update-index --assume-unchanged .idea/workspace.xml command. And to revert the setting: git update-index --no-assume-unchanged .idea/workspace.xml.

Useful links

Read the documentation at vaadin.com/docs.
Follow the tutorials at vaadin.com/tutorials.
Watch training videos and get certified at vaadin.com/learn/training.
Create new projects at start.vaadin.com.
Search UI components and their usage examples at vaadin.com/components.
Find a collection of solutions to common use cases in Vaadin Cookbook.
Find Add-ons at vaadin.com/directory.
Ask questions on Stack Overflow or join our Discord channel.
Report issues, create pull requests in GitHub.

For a full Vaadin application example, there are more choices available also from vaadin.com/start page.

skeleton-starter-flow's People

Contributors

Stargazers

Watchers

skeleton-starter-flow's Issues

MainView has both vertical and horizontal scrollbar

After #69 was merged Main view has both @BodySize(height = "100vh", width = "100vw") and setClassName("main-layout") adding margin: 20px; resulting in

Make Skeleton starter available in vcom

Need to fork the website and add the Starter there manually. Here is an example on doing the same for Beverage Buddy Starter: https://gitlab.vaadin.com/vaadincom/webpage/commit/6f267171d3883531dc9bd4111c9f6f9f57420ad2

The latest version of the starter should also be tagged with published tag to get it visible on the website.

Java icon appears in the dock when starting the server

When starting the application on OS X, a java icon appears in the Dock. This most likely happens because the new PWA features uses AWT for image manipulation, but the headless flag is not set.

Does not happen on the v11 branch.

Multiple Vaadin init messages during startup

When I start the application with the master branch, the console will print four separate messages about running in DEBUG MODE.

[qtp1658578510-15] WARN com.vaadin.flow.server.DefaultDeploymentConfiguration - 
===========================================================
Vaadin is running in DEBUG MODE.
Add productionMode=true to web.xml to disable debug features.
===========================================================
[qtp1658578510-15] WARN com.vaadin.flow.server.DefaultDeploymentConfiguration - 
===========================================================
Vaadin is running in DEBUG MODE.
Add productionMode=true to web.xml to disable debug features.
===========================================================
[qtp1658578510-14] WARN com.vaadin.flow.server.DefaultDeploymentConfiguration - 
===========================================================
Vaadin is running in DEBUG MODE.
Add productionMode=true to web.xml to disable debug features.
===========================================================
[qtp1658578510-14] WARN com.vaadin.flow.server.DefaultDeploymentConfiguration - 
===========================================================
Vaadin is running in DEBUG MODE.
Add productionMode=true to web.xml to disable debug features.
===========================================================

On the v11 branch, there is only one such message.

Something goes wrong when adding Grid to plain java starter

Setup:

Intelllij IDEA 2019.1
JDK 12
Maven 3.6.1 (and IDEA is using it, if I use Maven that IDEA includes there are even more issues)

Steps to reproduce:

Get plain java starter (RC1) from https://vaadin.com/start/latest/project-base
Extract zip and import it into your IDE
Run mvn jetty:run with your IDE
Let application start, and verify it works
Stop the jetty:run
Add Grid to MainView by adding following lines:
Grid<String> grid = new Grid<>(); add(grid);
Restart mvn jetty:run
Wait app to start and refresh the page

Expect outcome:
I see empty grid without columns in MainView with click me button.

Actual outcome:
Grid breaks the application on browser with: Uncaught DOMException: Failed to execute 'define' on 'CustomElementRegistry': the name "vaadin-grid-templatizer" has already been used with this registry and lots of 'undefined errors' follow.

Even if I run 'mvn clean install jetty:run' app is still broken same way.

Get rid of /src/main/frontend/ and use webapp folder instead

We need to put our resources into a single folder to eliminate the confusion that it's causing right now (based on DX tests and flow-bakery that had already implemented something similar).

To see how this feature may be implemented, refer to https://github.com/vaadin/patient-portal-demo-flow that had got rid of it recently.

Add Travis as a build service to the project and build it on each PR

Make Travis integration in the same way as it works for any demo/core projects.

It requires enabled Travis service for the repo and scripts in the repository.

V14: Upgrade webdrivermanager

The current license checker used in some Vaadin products (like AppSec Kit) use a transitive dependency of net.java.dev.jna:jna:5.13.0. This dependency is overriden by the webdrivermanager to a lower version where a method (present in the newer version) is missing. This causes the error reported in this issue.

We need to upgrade the webdrivermanager dependency to at least 5.3.2 to fix this.

There should be no `src` folder inside `frontend`

Unless there is a reason for that. I can't find any reason

Eclipse build loop

Importing the project in Eclipse, the build process loops indefinitely.

Replace "Vaadin Flow" by "Vaadin"

Since we want to avoid saying "Vaadin Flow" and replace it with "Vaadin" in general, we need to change the annotation @PWA(name = "Project Base for Vaadin Flow", shortName = "Project Base")

The example test suite should be as simple as possible

The ParallelTest and the Hub thingy is super-confusing to the initial learners of TestBench:

Don't use isHub or anything like that - it's not clear what value it provides to the programmer
Don't use parallelism: launching 6 browsers at a time is super-confusing at first. That is the first thing the user disables.

The MainTestIT and the AbstractViewTest should be as simple as possible. Simply extend from TestBenchTestCase instead of ParallelTest. It could be valuable to mention the ParallelTest in the javadoc somewhere, but let's not use it straight from the beginning.

JRebel reload goes horribly wrong

OpenJDK11, Vaadin 14 rc2, JRebel

Start app with jetty:run & JRebel.
App starts
Click button, get notification
Reload triggers for some reason
Server connection dialog is shown
Several more dialogs are shown, some with jetty directory listing

Production mode build doesn't work

Running with mvn jetty:run -Dvaadin.productionMode doesn't work in es5 nor in es6 version. The include path in ExampleTemplate.html is causing 404 about trying to load http://localhost:8080/bower_components/polymer/polymer.html If I change the path from /bower_components/polymer/polymer.html to bower_components/polymer/polymer.html the build works and loads http://localhost:8080/VAADIN/static/frontend/es6/bower_components/polymer/polymer.html It's strange as index.html has also root relative urls and those don't cause any 404.

Convert project to npm/p3/es6 modules support

Use branch 2.0 for now. Not sure if separate validation / snapshot build should be setup, as at some point this will be merged to master.

change @Route to @Route("")

This is much more clear to the users; it shows that this file is explicitly for the root, and other view can have other URLs

esbuild: Failed to install correctly

Trying to run this project master (which at the moment uses Vaadin 22.0.0) in my Tomcat fails with

[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - [webpack-dev-server] On Your Network (IPv4): http://192.168.0.17:36629/
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - [webpack-dev-server] Content not from webpack is served from '/home/mavi/work/vaadin/starters/14/skeleton-starter-flow/target/classes/META-INF/VAADIN/webapp, /home/mavi/work/vaadin/starters/14/skeleton-starter-flow/src/main/webapp' directory
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - /home/mavi/work/vaadin/starters/14/skeleton-starter-flow/node_modules/.pnpm/[email protected]/node_modules/esbuild/bin/esbuild:2
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - throw new Error(`esbuild: Failed to install correctly
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - ^
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - 
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - Error: esbuild: Failed to install correctly
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - 
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - Make sure you don't have "ignore-scripts" set to true. You can check this with
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - "npm config get ignore-scripts". If that returns true you can reset it back to
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - false using "npm config set ignore-scripts false" and then reinstall esbuild.
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - 
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - If you're using npm v7, make sure your package-lock.json file contains either
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - "lockfileVersion": 1 or the code "hasInstallScript": true. If it doesn't have
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - either of those, then it is likely the case that a known bug in npm v7 has
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - corrupted your package-lock.json file. Regenerating your package-lock.json file
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - should fix this issue.
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - 
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at Object.<anonymous> (/home/mavi/work/vaadin/starters/14/skeleton-starter-flow/node_modules/.pnpm/[email protected]/node_modules/esbuild/bin/esbuild:2:7)
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at Module._compile (internal/modules/cjs/loader.js:999:30)
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at Module.load (internal/modules/cjs/loader.js:863:32)
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at Function.Module._load (internal/modules/cjs/loader.js:708:14)
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at internal/main/run_main_module.js:17:47
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - 
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - ERROR in ./generated/vaadin.ts
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - Module build failed (from ../node_modules/.pnpm/[email protected][email protected]/node_modules/esbuild-loader/dist/index.js):
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - Error: The service was stopped
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at /home/mavi/work/vaadin/starters/14/skeleton-starter-flow/node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:1258:29
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at /home/mavi/work/vaadin/starters/14/skeleton-starter-flow/node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:611:9
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at Socket.afterClose (/home/mavi/work/vaadin/starters/14/skeleton-starter-flow/node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:589:7)
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at Socket.emit (events.js:326:22)
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at endReadableNT (_stream_readable.js:1241:12)
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at processTicksAndRejections (internal/process/task_queues.js:84:21)
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - 
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - ERROR in ../target/sw.ts
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - Module build failed (from ../node_modules/.pnpm/[email protected][email protected]/node_modules/esbuild-loader/dist/index.js):
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - Error: The service was stopped
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at /home/mavi/work/vaadin/starters/14/skeleton-starter-flow/node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:1258:29
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at /home/mavi/work/vaadin/starters/14/skeleton-starter-flow/node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:611:9
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at Socket.afterClose (/home/mavi/work/vaadin/starters/14/skeleton-starter-flow/node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:589:7)
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at Socket.emit (events.js:326:22)
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at endReadableNT (_stream_readable.js:1241:12)
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker -     at processTicksAndRejections (internal/process/task_queues.js:84:21)
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - 
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - ERROR in Can't find self.__WB_MANIFEST in your SW source.
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - [build-status] 3 errors and 0 warnings were reported.
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - [build-status] : Failed to compile.
[ForkJoinPool.commonPool-worker-19] INFO com.vaadin.base.devserver.AbstractDevServerRunner - Started Webpack. Time: 2695ms

------------------ Frontend compilation failed. ------------------

[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - Issues checking in progress...
[dev-server-output] INFO com.vaadin.base.devserver.DevServerOutputTracker - No issues found.
/home/mavi/local/apache-tomcat-9.0.44/bin/catalina.sh stop
Disconnected from the target VM, address: '127.0.0.1:33705', transport: 'socket'
NOTE: Picked up JDK_JAVA_OPTIONS:  --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
07-Dec-2021 12:59:41.898 INFO [main] org.apache.catalina.core.StandardServer.await A valid shutdown command was received via the shutdown port. Stopping the Server instance.
07-Dec-2021 12:59:41.898 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-8080"]
07-Dec-2021 12:59:41.905 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Catalina]
07-Dec-2021 12:59:41.973 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-8080"]
07-Dec-2021 12:59:42.003 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-8080"]
Disconnected from server

I've tried mvn vaadin:dance to no avail. I understand I could work around this issue by running npm config set ignore-scripts false but that's a security hole. Any tips on how to deal with this issue in a proper way please?

Environment: Ubuntu 21.10 x86-64, Vaadin 22.0.0, skeleton-starter-flow master, JDK 11

flow maven plugin fails on transpile-production-files with HtmlImport class missing

When I run mvn clean install -Dvaadin.productionMode the build fails:

[INFO] Scanning for projects...
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] Building Skeleton Starter for Vaadin Flow 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ skeleton ---
[INFO] Deleting /home/mavi/work/my/vok/skeleton-starter-flow/target
[INFO] 
[INFO] --- flow-maven-plugin:0.0.5:copy-production-files (default) @ skeleton ---
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ skeleton ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ skeleton ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 3 source files to /home/mavi/work/my/vok/skeleton-starter-flow/target/classes
[INFO] 
[INFO] --- flow-maven-plugin:0.0.5:transpile-production-files (default) @ skeleton ---
[INFO] Installing node version v8.9.0
[INFO] Downloading https://nodejs.org/dist/v8.9.0/node-v8.9.0-linux-x64.tar.gz to /home/mavi/work/my/vok/skeleton-starter-flow/target/cache/node-v8.9.0-linux-x64.tar.gz
[INFO] No proxies configured
[INFO] No proxy was configured, downloading directly
[INFO] Unpacking /home/mavi/work/my/vok/skeleton-starter-flow/target/cache/node-v8.9.0-linux-x64.tar.gz into /home/mavi/work/my/vok/skeleton-starter-flow/target/node/tmp
[INFO] Copying node binary from /home/mavi/work/my/vok/skeleton-starter-flow/target/node/tmp/node-v8.9.0-linux-x64/bin/node to /home/mavi/work/my/vok/skeleton-starter-flow/target/node/node
[INFO] Installed node locally.
[INFO] Installing Yarn version v1.3.2
[INFO] Downloading https://github.com/yarnpkg/yarn/releases/download/v1.3.2/yarn-v1.3.2.tar.gz to /home/mavi/work/my/vok/skeleton-starter-flow/target/cache/yarn-v1.3.2.tar.gz
[INFO] No proxies configured
[INFO] No proxy was configured, downloading directly
[INFO] Unpacking /home/mavi/work/my/vok/skeleton-starter-flow/target/cache/yarn-v1.3.2.tar.gz into /home/mavi/work/my/vok/skeleton-starter-flow/target/node/yarn
[INFO] Installed Yarn locally.
[INFO] Running 'yarn install' in /home/mavi/work/my/vok/skeleton-starter-flow/target
[INFO] yarn install v1.3.2
[INFO] [1/4] Resolving packages...
[INFO] [2/4] Fetching packages...
[INFO] [3/4] Linking dependencies...
[INFO] [4/4] Building fresh packages...
[INFO] success Saved lockfile.
[INFO] Done in 2.72s.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 18.585 s
[INFO] Finished at: 2018-01-27T12:10:40+02:00
[INFO] Final Memory: 62M/769M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.vaadin:flow-maven-plugin:0.0.5:transpile-production-files (default) on project skeleton: Execution default of goal com.vaadin:flow-maven-plugin:0.0.5:transpile-production-files failed: A required class was missing while executing com.vaadin:flow-maven-plugin:0.0.5:transpile-production-files: com/vaadin/ui/common/HtmlImport
[ERROR] -----------------------------------------------------
[ERROR] realm =    plugin>com.vaadin:flow-maven-plugin:0.0.5
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/home/mavi/.m2/repository/com/vaadin/flow-maven-plugin/0.0.5/flow-maven-plugin-0.0.5.jar
[ERROR] urls[1] = file:/home/mavi/.m2/repository/javax/enterprise/cdi-api/1.0/cdi-api-1.0.jar
[ERROR] urls[2] = file:/home/mavi/.m2/repository/javax/annotation/jsr250-api/1.0/jsr250-api-1.0.jar
[ERROR] urls[3] = file:/home/mavi/.m2/repository/org/eclipse/sisu/org.eclipse.sisu.inject/0.3.3/org.eclipse.sisu.inject-0.3.3.jar
[ERROR] urls[4] = file:/home/mavi/.m2/repository/org/apache/maven/maven-builder-support/3.5.0/maven-builder-support-3.5.0.jar
[ERROR] urls[5] = file:/home/mavi/.m2/repository/org/apache/maven/resolver/maven-resolver-util/1.0.3/maven-resolver-util-1.0.3.jar
[ERROR] urls[6] = file:/home/mavi/.m2/repository/org/apache/maven/shared/maven-shared-utils/3.1.0/maven-shared-utils-3.1.0.jar
[ERROR] urls[7] = file:/home/mavi/.m2/repository/com/google/inject/guice/4.0/guice-4.0-no_aop.jar
[ERROR] urls[8] = file:/home/mavi/.m2/repository/aopalliance/aopalliance/1.0/aopalliance-1.0.jar
[ERROR] urls[9] = file:/home/mavi/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.24/plexus-interpolation-1.24.jar
[ERROR] urls[10] = file:/home/mavi/.m2/repository/org/codehaus/plexus/plexus-utils/3.0.24/plexus-utils-3.0.24.jar
[ERROR] urls[11] = file:/home/mavi/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.7.1/plexus-component-annotations-1.7.1.jar
[ERROR] urls[12] = file:/home/mavi/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.4/plexus-sec-dispatcher-1.4.jar
[ERROR] urls[13] = file:/home/mavi/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[14] = file:/home/mavi/.m2/repository/org/apache/commons/commons-lang3/3.5/commons-lang3-3.5.jar
[ERROR] urls[15] = file:/home/mavi/.m2/repository/org/json/json/20171018/json-20171018.jar
[ERROR] urls[16] = file:/home/mavi/.m2/repository/commons-io/commons-io/2.6/commons-io-2.6.jar
[ERROR] urls[17] = file:/home/mavi/.m2/repository/com/github/eirslett/frontend-plugin-core/1.6/frontend-plugin-core-1.6.jar
[ERROR] urls[18] = file:/home/mavi/.m2/repository/org/codehaus/jackson/jackson-mapper-asl/1.9.13/jackson-mapper-asl-1.9.13.jar
[ERROR] urls[19] = file:/home/mavi/.m2/repository/org/codehaus/jackson/jackson-core-asl/1.9.13/jackson-core-asl-1.9.13.jar
[ERROR] urls[20] = file:/home/mavi/.m2/repository/org/apache/commons/commons-compress/1.5/commons-compress-1.5.jar
[ERROR] urls[21] = file:/home/mavi/.m2/repository/org/tukaani/xz/1.2/xz-1.2.jar
[ERROR] urls[22] = file:/home/mavi/.m2/repository/org/apache/commons/commons-exec/1.3/commons-exec-1.3.jar
[ERROR] urls[23] = file:/home/mavi/.m2/repository/org/apache/httpcomponents/httpclient/4.5.1/httpclient-4.5.1.jar
[ERROR] urls[24] = file:/home/mavi/.m2/repository/org/apache/httpcomponents/httpcore/4.4.3/httpcore-4.4.3.jar
[ERROR] urls[25] = file:/home/mavi/.m2/repository/commons-logging/commons-logging/1.2/commons-logging-1.2.jar
[ERROR] urls[26] = file:/home/mavi/.m2/repository/commons-codec/commons-codec/1.9/commons-codec-1.9.jar
[ERROR] urls[27] = file:/home/mavi/.m2/repository/org/reflections/reflections/0.9.11/reflections-0.9.11.jar
[ERROR] urls[28] = file:/home/mavi/.m2/repository/com/google/guava/guava/20.0/guava-20.0.jar
[ERROR] urls[29] = file:/home/mavi/.m2/repository/org/javassist/javassist/3.21.0-GA/javassist-3.21.0-GA.jar
[ERROR] urls[30] = file:/home/mavi/.m2/repository/com/vaadin/flow-server/1.0-SNAPSHOT/flow-server-1.0-SNAPSHOT.jar
[ERROR] urls[31] = file:/home/mavi/.m2/repository/com/vaadin/flow-push/1.0-SNAPSHOT/flow-push-1.0-SNAPSHOT.jar
[ERROR] urls[32] = file:/home/mavi/.m2/repository/com/vaadin/external/atmosphere/atmosphere-runtime/2.4.5.vaadin2/atmosphere-runtime-2.4.5.vaadin2.jar
[ERROR] urls[33] = file:/home/mavi/.m2/repository/com/vaadin/external/slf4j/vaadin-slf4j-jdk14/1.6.1/vaadin-slf4j-jdk14-1.6.1.jar
[ERROR] urls[34] = file:/home/mavi/.m2/repository/com/google/gwt/gwt-elemental/2.8.2/gwt-elemental-2.8.2.jar
[ERROR] urls[35] = file:/home/mavi/.m2/repository/commons-fileupload/commons-fileupload/1.3.3/commons-fileupload-1.3.3.jar
[ERROR] urls[36] = file:/home/mavi/.m2/repository/org/jsoup/jsoup/1.10.3/jsoup-1.10.3.jar
[ERROR] urls[37] = file:/home/mavi/.m2/repository/com/helger/ph-css/4.1.3/ph-css-4.1.3.jar
[ERROR] urls[38] = file:/home/mavi/.m2/repository/com/helger/ph-commons/6.2.4/ph-commons-6.2.4.jar
[ERROR] urls[39] = file:/home/mavi/.m2/repository/com/google/code/findbugs/annotations/2.0.3/annotations-2.0.3.jar
[ERROR] urls[40] = file:/home/mavi/.m2/repository/net/bytebuddy/byte-buddy/1.7.5/byte-buddy-1.7.5.jar
[ERROR] urls[41] = file:/home/mavi/.m2/repository/com/googlecode/gentyref/gentyref/1.2.0/gentyref-1.2.0.jar
[ERROR] urls[42] = file:/home/mavi/.m2/repository/org/webjars/webjars-locator-core/0.34/webjars-locator-core-0.34.jar
[ERROR] urls[43] = file:/home/mavi/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.7.3/jackson-core-2.7.3.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import  from realm ClassRealm[maven.api, parent: null]]
[ERROR] 
[ERROR] -----------------------------------------------------
[ERROR] : com.vaadin.ui.common.HtmlImport
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException

Review documentation PRs for beverage-app-starter-flow

Review these PRs:
vaadin/beverage-starter-flow#64
vaadin/beverage-starter-flow#80
vaadin/beverage-starter-flow#84

PWA names project as with Spring

The PWA annotation says that the project is with spring even though this is the non spring base starter.
@PWA(name = "Project Base for Vaadin Flow with Spring", shortName = "Project Base")

Apply @BodyStyle("height = 100vh, width = 100vw")

Add the styling for the <body> element using BodyStyle annotation on the main layout. This feature has been introduced in https://github.com/vaadin/flow/pull/3120/files

Rename https://github.com/vaadin/flow-application-skeleton to https://github.com/vaadin/skeleton-starter-flow

The name in readme and where ever linked should be Skeleton Starter for Flow

Update build process stuff and any documentation links in flow documentation, if necessary.

Production mode compilation shows warnings and errors

Some warnings:

[WARNING] The translated URL 'frontend://bower_components/vaadin-upload/theme/lumo/vaadin-upload-file.html' has no corresponding file on the filesystem, the file is addressed by path='/Users/mstahv/Downloads/my-starter-project-6/target/frontend/bower_components/vaadin-upload/theme/lumo/vaadin-upload-file.html'
[WARNING] The translated URL 'theme/lumo/example-template.html' has no corresponding file on the filesystem, the file is addressed by path='/Users/mstahv/Downloads/my-starter-project-6/target/frontend/theme/lumo/example-template.html'
[INFO] Installing re

And error:

[ERROR] warning "polymer-build > [email protected]" has incorrect peer dependency "polymer-analyzer@^3.0.0-pre.17 || ^3.0.0".

Remove workspace.xml from git & add it to .gitignore

Currently Intellij's .idea/workspace.xml is committed to git. That has the following disadvantages:

anytime I open the project, Intellij changes the file immediately, immediately showing that there are git changes in the project.
Performing git reset --hard throws away those changes including any launch configurations I've defined, which is really annoying.

error with 14.9.0 under dev-mode

Upgrade project to 14.9.0 failed with error when building under dev mode

java.lang.NoClassDefFoundError: com/vaadin/pro/licensechecker/LicenseChecker

step to reproduce:

take this branch #638
run mvn install -Pit
(make sure you are using JAVA 8.)

Add custom style

In the current app starter there is read me file in the folder where custom style html file should be. It would be better to have simple style html file there and use it in main view.

Idea behind of this feature request is, that it is really commonly asked question and developers to struggle to get it right (i.e. paths, correct annotation, etc.)

V15 version is no longer a PWA

Startup says

[main] ERROR com.vaadin.flow.server.startup.VaadinAppShellInitializer - 

Found app shell configuration annotations in non `AppShellConfigurator` classes.
Please create a custom class implementing `AppShellConfigurator` and move the following annotations to it:
    - @PWA from org.vaadin.artur.MainView

Please upload 14.7.8 artifacts to maven central or downgrade the starter to 14.7.7.

Thanks!