You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rolfkleef opened this issue
Feb 14, 2022
· 0 comments
Labels
DebtRemoval of impedements to future development (architecture changes, refactoring, infrastructure)EpicS2IUpdates and changes related to spreadsheet conversions
We started working with Ant to benefit from build tool features, such as only processing a file when it is newer than the targeted output, and declarative specification of steps.
Together with Saxon-HE and BaseX, this resulted in a Java-oriented stack.
In the "pure S2I" version, the transformation steps are more linear and straightforward, and since we're running each conversion "once per container", much of the benefit of a tool like Ant is no longer used.
In the meantime, there is a nodejs-based version of Saxon. As we're trying to eliminate (bulky) components from the convertor, we can test conversion performance of both Saxon versions, and perhaps consolidate on a pure-node/javascript stack.
The text was updated successfully, but these errors were encountered:
rolfkleef
added
Debt
Removal of impedements to future development (architecture changes, refactoring, infrastructure)
S2I
Updates and changes related to spreadsheet conversions
Epic
labels
Feb 14, 2022
DebtRemoval of impedements to future development (architecture changes, refactoring, infrastructure)EpicS2IUpdates and changes related to spreadsheet conversions
We started working with Ant to benefit from build tool features, such as only processing a file when it is newer than the targeted output, and declarative specification of steps.
Together with Saxon-HE and BaseX, this resulted in a Java-oriented stack.
In the "pure S2I" version, the transformation steps are more linear and straightforward, and since we're running each conversion "once per container", much of the benefit of a tool like Ant is no longer used.
In the meantime, there is a nodejs-based version of Saxon. As we're trying to eliminate (bulky) components from the convertor, we can test conversion performance of both Saxon versions, and perhaps consolidate on a pure-node/javascript stack.
The text was updated successfully, but these errors were encountered: