As mentioned it in JBeret 1.3.0.Beta7 release announcement thread, jberet-rest-api module (in 1.3.0.Beta6 or earlier) has been split into jberet-rest-commons and jberet-rest-api modules starting 1.3.0.Beta7. Now the new structure is:
jberet-rest
├── jberet-rest-api
│ ├── src
│ └── target
├── jberet-rest-commons
│ ├── src
│ └── target
The parent module jberet-rest now contains 2 sub-modules:
* jberet-rest-commons: common classes (DTO and service classes) for implementing JBeret REST API, regardless of the REST frameworks.
org/jberet/rest/entity/AbstractExecutionEntity.java
org/jberet/rest/entity/JobExecutionEntity.java
org/jberet/rest/entity/BatchExceptionEntity.java
org/jberet/rest/entity/JobInstanceEntity.java
org/jberet/rest/entity/JobEntity.java
org/jberet/rest/entity/MetricEntity.java
org/jberet/rest/entity/StepExecutionEntity.java
org/jberet/rest/service/JobService.java
* jberet-rest-api: REST API implementation based on JAX-RS (JAX-RS resource classes and client class)
org/jberet/rest/provider/CORSFilter.java
org/jberet/rest/_private/RestAPILogger.java
org/jberet/rest/_private/RestAPIMessages.java
org/jberet/rest/resource/JobScheduleResource.java
org/jberet/rest/resource/JobResource.java
org/jberet/rest/resource/JobInstanceResource.java
org/jberet/rest/resource/JobExecutionResource.java
org/jberet/rest/exception/BatchExceptionMapper.java
org/jberet/rest/client/BatchClient.java
You can see details in the related JIRA issue below, but the main motive is to reuse common components across REST API impls with different REST frameworks, such as JAX-RS, Vert.x and Spring.
[JBERET-360] - Split jberet-rest-api module into jberet-rest-commons and jberet-rest-api modules
Feedback are welcome. Should you encouter any issues using the new artifacts, please report it in this forum or file JIRA issues, or Github issues
