JakartaMigration

# Migration Strategy Definitions
# Format: strategy.{name}.property=value

# Big Bang Strategy
strategy.big_bang.displayName=Big Bang
strategy.big_bang.description=Migrate everything at once
strategy.big_bang.benefits=• Migrate all javax dependencies to Jakarta EE at once\n• Single comprehensive change\n• Best for small, self-contained projects\n• Requires thorough testing before starting
strategy.big_bang.risks=• Higher risk - issues affect entire codebase\n• Longer rollback time if problems occur\n• Requires comprehensive test suite\n• May cause extended downtime during migration
strategy.big_bang.color=220,53,69

# Incremental Strategy
strategy.incremental.displayName=Incremental
strategy.incremental.description=One dependency at a time
strategy.incremental.benefits=• Migrate dependencies incrementally\n• Update one dependency, test, then proceed\n• Lower risk per change\n• Best for large, complex projects
strategy.incremental.risks=• Longer overall migration timeline\n• Must maintain compatibility during transition\n• May require temporary dual dependencies\n• Need careful dependency ordering
strategy.incremental.color=255,193,7

# Transform Strategy
strategy.transform.displayName=Transform
strategy.transform.description=Combined build and runtime transformation
strategy.transform.benefits=• Combine build-time and runtime transformation approaches\n• Use OpenRewrite for automated code changes\n• Deploy runtime adapters for edge cases\n• Best for complex enterprise applications
strategy.transform.risks=• Most complex implementation\n• Requires both build and runtime configuration\n• Higher resource overhead\n• May need specialized expertise
strategy.transform.color=23,162,184

# Microservices Strategy
strategy.microservices.displayName=Microservices
strategy.microservices.description=Migrate each service independently
strategy.microservices.benefits=• Migrate microservices one at a time\n• Each service can use different strategy\n• Independent deployment and testing\n• Best for distributed architectures
strategy.microservices.risks=• Requires coordination across services\n• Inter-service dependencies must be handled\n• May need service mesh updates\n• Longer overall migration timeline
strategy.microservices.color=108,117,125

# Adapter Pattern Strategy (NEW)
strategy.adapter.displayName=Adapter Pattern
strategy.adapter.description=Use adapter classes for javax/jakarta compatibility
strategy.adapter.benefits=• Maintain backward compatibility during migration\n• Gradual replacement of javax with jakarta\n• Lower risk changes\n• Easy to rollback individual adapters
strategy.adapter.risks=• Additional code maintenance\n• Runtime overhead for adapter layer\n• More complex classpath management\n• Need to track adapter usage
strategy.adapter.color=111,66,193