-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Move infrastructure APIs under a specific package #5014
Copy link
Copy link
Closed
Labels
api: breaking-changeIssues that require or introduce an API breaking changeIssues that require or introduce an API breaking changein: infrastructurestatus: for-internal-teamIssues that are planned to be resolved by the Spring Batch team, and not open for contributions.Issues that are planned to be resolved by the Spring Batch team, and not open for contributions.type: enhancement
Milestone
Metadata
Metadata
Assignees
Labels
api: breaking-changeIssues that require or introduce an API breaking changeIssues that require or introduce an API breaking changein: infrastructurestatus: for-internal-teamIssues that are planned to be resolved by the Spring Batch team, and not open for contributions.Issues that are planned to be resolved by the Spring Batch team, and not open for contributions.type: enhancement
Type
Fields
Give feedbackNo fields configured for issues without a type.
As of v5.2, all public APIs of a given module are under a specific package (
org.springframework.batch.coreinspring-batch-core,org.springframework.batch.testinspring-batch-test, etc) exceptspring-batch-infrastructure.Infrastructure APIs are under
org.springframework.batch.*which makes them difficult to distinguish from other APIs. For example, it is not clear iforg.springframework.batch.item.ExecutionContextis an infrastructure concept or a core concept. And by the way,ExecutionContextis currently in theinfrastructuremodule while it should be in thecoremodule (every step has its execution context and not only item oriented steps).