|
|
|
Re: New Scout version 10 released [message #1823419 is a reply to message #1823413] |
Thu, 26 March 2020 10:45 |
Mr Robot Messages: 71 Registered: March 2020 |
Member |
|
|
Hello,
1. I downloaded new eclipse.
2. Created new project using create new project wizard
3. Installed node 12
4. Run appliucation using "web all"
When I run application, like this it is ok, no filter for login is set. I can see application.
But if I set devMode in config.properties to false when I run application I have that error.
I did not install any sample app, only created new project, not JS project...
I started application on localhost:8082 a link that is available in console when app is started
I am using win10
[Updated on: Thu, 26 March 2020 10:47] Report message to a moderator
|
|
|
|
Re: New Scout version 10 released [message #1823435 is a reply to message #1823426] |
Thu, 26 March 2020 16:04 |
Claudio Guglielmo Messages: 7 Registered: May 2014 |
Junior Member |
|
|
Ok, you explicitly set devMode to false. This works a little bit different than for previous releases.
When the server runs in dev mode, it loads the html files from the dist/dev folder. The dist folder contains the output of the webpack build and other html resources.
When the server runs in prod mode (devMode=false), the resources are loaded from the class path. So the content of the dist folder needs to be in the folder target/classes, e.g. target/classes/dev and target/classes/res. This is done by the maven phase prepare-package and should be executed automatically in Eclipse. Additionally, in prod mode the JS and CSS files look different than in dev mode, they are minimized and obfuscated. And they are placed in a folder prod.
Since creating these resources is not necessary for the daily development, you need to trigger the build manually. To do so, run "npm run build:prod" on the command line. This will fill your folder dist/prod. Now you need to move the prod folder to target/classes. Either do it manually or you can also click "Project / Clean..." in Eclipse which should do it for you.
Note: When building the war file using mvn install, this should all be done automatically. So when deploying it on Tomcat it should work out of the box.
|
|
|
|
|
Re: New Scout version 10 released [message #1830756 is a reply to message #1830716] |
Mon, 03 August 2020 10:32 |
Patrick Baenziger Messages: 96 Registered: September 2011 |
Member |
|
|
Hi Senaka
Welcome to Eclipse Scout!
To better help you, could you provide us with the info what your JDK/JRE is that you are running Maven with, as well as the Maven version.
The easiest way to do is:
* If you are running the Maven Build from the commandline, please paste the output of mvn -version
* If you are running the Maven Build from the Eclipse IDE, open the Debug Menu and select the Build you ran. Check "Debug output" and start it again.
The output should look something like this:
Maven home: C:\dev\apache-maven-3.5.4
Java version: 11.0.4, vendor: AdoptOpenJDK, runtime: C:\eclipse\java\adoptopenjdk-11.0.4
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04119 seconds