When UberJar is generated for separate deploy, local.app.properties file is generated automatically. In this file, we can see some pre-defined properties that override $profile$-app.properties settings.
In order to change generated local.app.properties, you have to define "default" properties in the build.gradle file, so there is no point in creating profile file.
Example of the default local.app.properties for core:
In this case, it is almost impossible to override the property cuba.webPort, you have to set it using command line, which is not great.
I'd suggest making these "default" properties explicit in the build task parameters and do not generate them at all if they are not specified in the task. Default values can be included in app.properties/web-app.properties though. Can be related to issue #135
Environment
Description of the bug or enhancement
When UberJar is generated for separate deploy,
local.app.properties
file is generated automatically. In this file, we can see some pre-defined properties that override$profile$-app.properties
settings.In order to change generated
local.app.properties
, you have to define "default" properties in thebuild.gradle
file, so there is no point in creating profile file.Example of the default
local.app.properties
for core:In this case, it is almost impossible to override the property
cuba.webPort
, you have to set it using command line, which is not great.I'd suggest making these "default" properties explicit in the build task parameters and do not generate them at all if they are not specified in the task. Default values can be included in
app.properties
/web-app.properties
though. Can be related to issue #135