You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to enable production mode for flow-test-root-context module.
There are a number of issue with that but if flow-test-resources dependency is removed then I get the error:
Execution default of goal com.vaadin:flow-maven-plugin:1.0-SNAPSHOT:package-for-production failed: The fragment file path 'frontend/com/vaadin/flow/uitest/ui/frontend/consoleLoggingProxy.js' was resolved to '/Users/denis/workspace/flow/flow-tests/test-root-context/target/frontend/frontend/com/vaadin/flow/uitest/ui/frontend/consoleLoggingProxy.js', which either does not exist or not a file.
The error is caused by the class BrowserLoggingView which has this declaration:
@JavaScript(value = "context://frontend/com/vaadin/flow/uitest/ui/frontend/consoleLoggingProxy.js", loadMode = LoadMode.INLINE)
public class BrowserLoggingView extends Div {
The class uses context schema instead of frontend but the path starts with frontend/ which should be resolved to the the same path as frontend:// schema. But the maven plugin uses frontend prefix to find the file so context:// schema behaves in the same way as frontend:// schema.
The text was updated successfully, but these errors were encountered:
I'm trying to enable production mode for
flow-test-root-context
module.There are a number of issue with that but if
flow-test-resources
dependency is removed then I get the error:The error is caused by the class
BrowserLoggingView
which has this declaration:The class uses
context
schema instead offrontend
but the path starts withfrontend/
which should be resolved to the the same path asfrontend://
schema. But the maven plugin usesfrontend
prefix to find the file socontext://
schema behaves in the same way asfrontend://
schema.The text was updated successfully, but these errors were encountered: