Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug #10769 #23

Merged
merged 3 commits into from Sep 24, 2019
Merged

Bug #10769 #23

merged 3 commits into from Sep 24, 2019

Conversation

mmoqui
Copy link
Member

@mmoqui mmoqui commented Aug 5, 2019

Restructure the different sections of settings of the plugin SilverSetup in
order to separate correctly what are for configuration of Silverpeas, what
are for installation and what are for the migration of the data source.

Add a new plugin setting property: timeout. It sets the timeout of the
waiting for JBoss to answer to the requests sent by the plugin. By
default it is set to 5mn (instead of 2mn) but it can be changed by
setting the property
silversetup {
timeout =
}
in the SILVERPEAS_HOME/bin/build.gradle file.

Don't forget to merge then the PR Silverpeas/Silverpeas-Distribution#5

Restructure the different sections of settings of the plugin SilverSetup in
order to separate correctly what are for configuration of Silverpeas, what
are for installation and what are for the migration of the data source.

Add a new plugin setting property: timeout. It sets the timeout of the
waiting for JBoss to answer to the requests sent by the plugin. By
default it is set to 5mn (instead of 2mn) but it can be changed by
setting the property
silversetup {
  timeout = <the number of milliseconds to wait for>
}
in the SILVERPEAS_HOME/bin/build.gradle file.
Add a new configuration property to set the timeout of the application
deployment of Wildfly: SERVER_STARTING_TIMEOUT. By default it is set to 5mn
(300 seconds) as it is by default in Wildfly.
This parameter can then be modified in the config.properties of the Silverpeas
distribution.
Fix the development mode checking.
Fix the command status parsing with CLI scripts (in JBossServer)

Add a way to specify a default value in variable placeholders in an expression.
For example, a variable without default value can be used as before in an
expression: ${MY_VARIABLE}.
Beside that, a default value can be indicated as such: ${MY_VARIABLE:true}
the semi-colon is used as the separator between the variable name and its
default value. When the variable placeholder is encountered within an
expression and it has no values set (for example in the config.properties),
then the default value is used to replace the variable placehodler.
@SilverYoCha SilverYoCha self-assigned this Sep 23, 2019
@SilverYoCha SilverYoCha merged commit 074737d into Silverpeas:master Sep 24, 2019
@mmoqui mmoqui deleted the bug-10769 branch September 24, 2019 08:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants