Thank you for your work. I get this error when updating to 1.1.1 and Vaadin

Directory ClipboardHelper
1

Thank you for your work. I get this error when updating to 1.1.1 and Vaadin 14 with npm:

Running project in development mode with no access to folder '/mnt/c/dev/clipboardhelper'.

I’m on Windows.
This happens when trying to load the application
Can you help me please?

2

Try if 1.1.2 works better.

3

This is still happening with 1.1.2 and 1.1.1 on MacOS

4

Can you create a small project that reproduces the issue?

5 
Caused by: java.lang.IllegalStateException: Running project in development mode with no access to folder '/mnt/c/dev/clipboardhelper'.
Build project in production mode instead, see https://vaadin.com/docs/v14/flow/production/tutorial-production-mode-basic.html

I’m running v14 compatibity mode on tomcat, is some of that a problem?

https://github.com/kolle1986/my-clipboard-helper-vaadin

6

I don’t know without a project to reproduce the issue.

7

Sorry, I edited my previous reply with github source code link

8

Any progress with this?

9

No, haven’t had time to look at it yet, sorry.

10

Okay, I finally had time to look at this. I cloned the sample project, made sure I don’t have /mnt/c/dev/clipboardhelper in place on my computer, ran mvn jetty:run . Example starts and runs ok. Can you help me further with the example?

11

Starting on tomcat error:

Caused by: java.lang.IllegalStateException: Running project in development mode with no access to folder '/mnt/c/dev/clipboardhelper'.
Build project in production mode instead, see https://vaadin.com/docs/v14/flow/production/tutorial-production-mode-basic.html
	at com.vaadin.flow.server.DeploymentConfigurationFactory.verifyFolderExists(DeploymentConfigurationFactory.java:397)
	at com.vaadin.flow.server.DeploymentConfigurationFactory.readBuildInfo(DeploymentConfigurationFactory.java:201)
	at com.vaadin.flow.server.DeploymentConfigurationFactory.createInitParameters(DeploymentConfigurationFactory.java:172)
	at com.vaadin.flow.server.DeploymentConfigurationFactory.createPropertyDeploymentConfiguration(DeploymentConfigurationFactory.java:133)
	at com.vaadin.flow.server.startup.ServletDeployer$StubServletConfig.createDeploymentConfiguration(ServletDeployer.java:145)
	at com.vaadin.flow.server.startup.DevModeInitializer.onStartup(DevModeInitializer.java:180)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5080)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
	... 29 more
12

I ran mvn clean package -Pproduction and deployed the resulting .war file on to a Tomcat, still works ok for me

13

Yes, strange, mvn clean package -Pproduction also works for me, but running in dev mode doesn’t. Don’t know why?!

14

dev mode only really works with e.g. the Maven Jetty plugin or similar

15

I’m running version 1.0.1 of clipboardhelper and it works ok, but with 1.1.2 this error happens on startup tomcat. Found this thread : https://vaadin.com/forum/thread/17872302/error-running-project-in-development-mode-with-no-access-to-folder-tomcat-8 but I’m running compatibility mode without npm just webjars and I don’t have maven plugin prepare-frontend .

16

Your sample project seems to be in npm mode, not compatibility mode?

17

Sorry, I managed now to run sample project, but my primary project still has the same error.

18

Ok, are you able to modify the sample project so that it fails?

19

Yes, when you remove <build> block from pom.xml you get this error. I can send you pom.xml from my primary project if you can tell what could be done to fix this. I know problem is compatibility mode but don’t know how to get it work. Thanks for you effort anyway.

And yes, when I add build block from sample project to my primary project than it fails with npm errors, webpack…