Deprecated Property Scanning Config
Configuration for conditional property scanning during migration.
Controls which packages are scanned for deprecated property in @ConditionalOnProperty annotations. Uses a flexible approach with configurable include/exclude patterns to handle diverse project structures and dependencies.
Spring Boot + Kotlin Binding Pattern Consistency
All properties use var
to ensure consistency with production requirements:
@Configuration + @ConfigurationProperties: Requires
var
for CGLIB proxy compatibilityComplex types (List): Need
var
for reliable environment variable bindingScalar types: Use
var
to maintain pattern consistency and avoid production issues
This follows the same pattern as DeprecatedPropertyWarningConfig
which was validated in production.
See also
for detailed production lesson learned documentation
Properties
Additional user-specific packages to exclude. Allows runtime customization without modifying the default exclusion list.
Whether to use classpath-based detection to automatically exclude JAR-based packages. When enabled, packages from JAR files are automatically excluded from scanning.
Package prefixes to exclude from scanning. Uses a comprehensive strategy that excludes common framework and library packages while allowing configuration override for custom environments.
Base packages to scan for deprecated conditional annotations. Defaults to actual Embabel packages while excluding framework internals.
Maximum depth for package scanning to prevent excessive recursion.