Some rows have backfilled times that are duplicates, causing the join to
join multiple rows. Assume ids only increment and fetch the row with the
highest id instead, and join on id.
Set maven package versions to variables and defining the variables in the parent pom when the package is used in multiple modules
Upgrade maven packages
Prevent trimming stack trace to maven surefire which caused newer versions to not display stacktrace in Netbeans.
Upgrade Maven jar plugin from 3.0.2 to 3.1.1
Upgrade Maven compiler plugin version from 3.6.1 to 3.8.0
Upgrade Maven checkstyle plugin version from 2.17 to 3.0.0
Upgrade Maven javadoc plugin from 3.0.0-M1 to 3.1.0
Upgrade Maven surefire plugin from 2.18 to 2.22
Upgrade Maven plugin api from 3.0.5 to 3.6.1
Upgrade Maven plugin annotations from 3.4 to 3.6.0
Upgrade Maven plugin plugin from 3.4 to 3.6.0
Upgrade Maven git commit id plugin from 2.2.5 to 2.2.6
Upgrade Maven jarsigner plugin from 1.4 to 3.0.0
Upgrade Maven resource plugin from 3.0.2 to 3.1.0
This world type is not specifically a PVP world type; at the time of
this commit, world 365 is a non-PVP high-risk world, where the world is
the same as a regular members' world, except that the Protect Item
prayer is disabled.
- Remove spring boot test (no longer necessary)
- Move test development configuration to main package
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
This is a much more natural fit for the config service which is really a
key value store, and has been abusing SQL. This will let us expand the
config stuff later to support profiles and per-account config values.
I have left in the SQL code for now so config changes are still being
sent there in the event of catastrophic mongodb failure.
Instead of replacing configuration with test configuration on classpath,
create test profile and use that.
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
- Instead of replacing configuration with dev configuration on classpath,
create dev profile and use that
- Move common properties to application.yaml
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
The exclude is supposed to be on SpringBootApplication annotation,
otherwise IntelliJ Spring plugin errors, and also SpringBootApplication
already contains EnableAutoConfiguration.
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
