chrislu
f20bad97e4
fix: force Maven update and verify JAR contains updated code
...
Added -U flag to mvn install to force dependency updates
Added verification step using javap to check compiled bytecode
This will show if the JAR actually contains the new logging code:
- If 'totalPosition' string is found → JAR is updated
- If not found → Something is wrong with the build
The verification output will help diagnose why INFO logs aren't showing.
2025-11-23 10:15:29 -08:00
..
2025-08-11 15:06:14 -07:00
2025-08-11 15:06:14 -07:00
2025-08-11 15:06:14 -07:00
2025-08-11 15:06:14 -07:00
2025-08-11 15:06:14 -07:00
2025-08-11 15:06:14 -07:00
2025-08-11 15:06:14 -07:00
2025-10-16 12:42:53 -07:00
2025-11-10 11:54:54 -08:00
2025-11-19 20:06:57 -08:00
2025-11-10 11:54:54 -08:00
2025-11-10 11:54:54 -08:00
2025-11-10 11:54:54 -08:00
2025-11-10 11:54:54 -08:00
2025-11-10 11:54:54 -08:00
2025-11-10 11:54:54 -08:00
2025-11-19 20:06:57 -08:00
2025-11-10 11:54:45 -08:00
2025-09-08 11:35:01 -07:00
2025-11-17 21:20:59 -08:00
2025-10-27 09:22:17 -07:00
2025-10-27 09:22:17 -07:00
2025-10-20 16:46:55 -07:00
2025-10-16 12:42:12 -07:00
2025-11-10 11:55:02 -08:00
2025-11-19 21:22:18 -08:00
2025-11-19 21:22:18 -08:00
2025-10-20 16:46:55 -07:00
2025-11-18 12:06:56 -08:00
2025-10-27 09:22:17 -07:00
2025-10-27 09:22:17 -07:00
2025-10-27 09:22:17 -07:00
2025-10-27 09:22:17 -07:00
2025-11-21 11:18:32 -08:00
2025-11-18 23:18:35 -08:00
2025-11-18 23:18:35 -08:00
2025-11-23 10:15:29 -08:00
2025-11-18 23:18:35 -08:00