- The current master branch doesn't work at ETL, I am researching which commit introduces this problem.
- This repo is NOT the same as the community EPICS Archiver Appliances, so please be aware about the modification here, here is the link, https://github.com/archiver-appliance/epicsarchiverap.git , one can move out of this repository
- Will cherry pick code changes only for the archiver appliance codes, NOT tests, styles, and so on
- Will test it within a local environment accordingly
- Will not Release and Tag within history
This repository uses a legacy build system that is different from the community EPICS archiver appliance repository, which recently became inoperable due to the removal of the Ant build system.
Migrating to the community's Gradle build system is challenging. Our resource constraints and lack of familiarity with Gradle make adoption difficult. There's no clear benefit to learning Gradle for our specific needs (accelerator control system) at this time.
In addition, the current build system has significant drawbacks:
- Requires a specific and recent version of Gradle.
- Uses a mix of Gradle styles (Kotlin and Groovy), making it difficult to understand and maintain.
- Relies on the Gradle wrapper, which prevents standard Gradle build commands from using the system's default version of Gradle. Debian 12 has the version 4.4.1.
Given these factors and the wider adoption of Maven in the Java applications with the EPICS comunity, migrating to Maven may be a more strategic choice.
In my opinion, migrating to Tomcat 10 should be a higher priority than building the system itself.
Thanks Git for diverting our works easily every before.
The baseline of this repository from 835061f and the following individual commits are selected due to my own reviews
- Commit
dea7acb - Commit
8b4f22e
See void/ for more documentations