Fixed startDate from dynamic current year to hardcoded 2025 in
testPostInterestNotZero() to maintain consistent 2025 timeline.
Resolves HTTP 400 error caused by date mismatches.
Fixed misspelled 'allowPartialPeriodInterestCalcualtion' to
'allowPartialPeriodInterestCalculation' in REST API and code.
35 files updated as specified in JIRA.
The extractBooleanNamed method can return null when the JSON value is null
or missing. Using primitive boolean causes automatic unboxing which throws
NullPointerException.
Changes:
- CalendarCommandFromApiJsonDeserializer: Use Boolean wrapper instead of
primitive boolean for 'repeating' field extraction
- CalendarCommandFromApiJsonDeserializer: Use Boolean.TRUE.equals() for
null-safe boolean comparison
- CalendarCommand: Update field type and constructor parameter from
boolean to Boolean to support null values
This addresses the FIXME comments on lines 156 and 298 in the original file.
* Go analog for step 15, automation was broken.
* Fix two admonitions: I meant to use `NOTE`. `INFO` is not a valid admonition in asciidoc, so it just shows up as text.
* release/1.14.0:
update manual release instructions
port steps 10 & 11 to the ATR
docs: adapt artifact checks to new ATR tool
improve svn release staging/release instructions
exclude jquery-1.7.min.js from source release
ignore .swp files when building src release
add license to .mailmap
add RAT excludes for ATR
add license to scripts/*.sh
fix both NOTICE files for ATR
doc: remove errant config
improve start release notes wording in step 3
Not gonna lie, I'm getting tired of maintaining this second source of truth. Hopefully my laziness, impatience, and hubris will tip the scales far enough to delete it.
We're already reaping rewards for using ATR (checks+voting+email support), and I want us to do both the old way AND the new way for now. I'll consider the old release process in "soft deprecation" as the ATR matures.
All good. I tested these just now.
ATR so far does artifact checks & voting/email management.
Working with artifacts on the svn server is still our responsibility, for now.
This is to workaround an issue, UI misunderstanding, or PEBKAC with the ATR (ASF Trusted Releases) tool wherein I am unable to exclude the license header check for this file. jQuery (and its dependencies) can be used entirely under the MIT, see <https://jquery.com/license/>.
Once https://github.com/apache/tooling-trusted-releases/issues/312 ... is resolved we should be able to revert this workaround.
While this workaround is in place, consumers of apiLive.htm must:
1. put a copy of jquery-1.7.min.js next to apiLive.htm
2. change apiLive.htm to refer to jquery-1.7.min.js on a CDN
If someone needing apiLive.htm prefers the first option, they can grab a copy at https://code.jquery.com/jquery-1.7.min.js .
If they prefer the second option, they can pick a minified or unminified link listed at https://blog.jquery.com/2011/11/03/jquery-1-7-released/ and modify line 6 of apiLive.htm to refer to that instead, for example:
- <script type="text/javascript" src="jquery-1.7.min.js"></script>
+ <script type="text/javascript" src="https://code.jquery.com/jquery-1.7.min.js"></script>
There are other ways to deal with the license header check as well. For example: We could use 2nd option above (always), or finally/actually port away from apiLive.htm (it is in legacy-docs, after all).
similar to 45404bafba
All asciidoctor config must be in `fineract-doc/src/docs/en/config.adoc`.
In this case `:sectnums:` re-starts ToC section numbering partway through the ToC.
