yasithdev opened a new pull request, #679: URL: https://github.com/apache/airavata/pull/679
Thirty unreferenced classes under `orchestration-service/task` plus `email-config.yaml` — leftover scaffolding from the pre-DB-transactional-executor (Helix/gfac) era. A **closed set** that nothing live references (the reactor compiles cleanly without it): - **Email-monitor parsing**: `EmailParser` + PBS/SLURM/UGE/LSF/HTCondor/AiravataCustom parsers + `ResourceConfig` + `email-config.yaml`. (Live monitoring uses squeue polling; `ServerSettings.getEmailBasedMonitorAddress`, still used by GroovyMapBuilder, is kept.) - **`IServer` lifecycle** + its 3 impls (`DataInterpreterService`, `ProcessReschedulingService`, `ComputationalResourceMonitoringService`) + `DataAnalyzer(Impl)`. The impls carry **no Spring stereotype**, so component-scan never instantiated them. - **Scanner/scheduler/rescheduler** cluster (6 files). - **Orphaned leaves** (10 files): monitor/parsing/constants classes. ## Test plan - `mvn install -DskipTests` (full reactor) green — fails if any live code referenced the set. - No `@Component`/`@Service`/lifecycle stereotype among the deleted files (grep), so the Spring context + deployed jar behavior are unchanged. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
