mocode-software/meldestelle
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
d87a5a4a93
meldestelle/docs/migration-status.md
stefan a256622f37 refactor: Migrate from monolithic to modular architecture 
- Restructure project into domain-specific modules (core, masterdata, members, horses, events, infrastructure)
- Create shared client components in common-ui module
- Implement CI/CD workflows with GitHub Actions
- Consolidate documentation in docs directory
- Remove deprecated modules and documentation files
- Add cleanup and migration scripts for transition
- Update README with new project structure and setup instructions
2025-07-22 18:44:18 +02:00

2.3 KiB
Raw Blame History

Migration Status

This document provides an overview of the current status of the migration from the old module structure to the new module structure.

Completed Tasks

  1. Migration of Code

    • All code has been migrated from the old modules to the new modules
    • Package declarations have been updated to match the new structure
    • Imports have been updated to reflect the new package structure

  2. Build Configuration

    • Build files (build.gradle.kts) have been updated for all modules
    • Dependencies have been configured correctly
    • Application plugins and mainClass configurations have been added to API modules

  3. Infrastructure/Gateway Module

    • Fixed unresolved references in ApiIntegrationTest.kt
    • Created ApiGatewayInfo and HealthStatus classes
    • Updated to use ApiResponse instead of BaseDto
    • Renamed verifyBaseDtoStructure to verifyApiResponseStructure
    • Updated build.gradle.kts to allow compilation but exclude from test execution

  4. Verification

    • Build passes when skipping tests
    • All modules compile successfully

Remaining Tasks

See Migration Remaining Tasks for a detailed list of remaining tasks.

  1. Fix Test Issues in Client/Web-App Module

    • Fix unresolved references in test files

  2. Complete Client Module Migration

    • Fix excluded React-based components in Common-UI Module
    • Fix excluded screens and viewmodels in Web-App Module
    • Implement proper desktop application functionality in Desktop-App Module

  3. Verify Cross-Module Dependencies

    • Ensure all modules have the correct dependencies
    • Check for circular dependencies
    • Optimize dependency versions

  4. Update Documentation

    • Update README.md with new module structure
    • Document the new architecture
    • Update development guidelines

  5. Performance Testing

    • Run performance tests to ensure the new structure doesn't impact performance
    • Optimize build times

  6. Update CI/CD Pipeline

    • Update CI/CD pipeline to work with the new module structure
    • Ensure all tests run in the pipeline

Next Steps

The next priority should be to fix the test issues in the Client/Web-App Module, followed by completing the Client Module Migration. This will ensure that the client-side code is fully functional with the new module structure.