Details
-
Type:
Improvement Request
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.3.0
-
Fix Version/s: 2.4.0
-
Component/s: None
-
Security Level: Public
-
- Environment:
- -
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Christophe DENEUX [ cdeneux ] | Victor NOËL [ vnoel ] |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] |
| Description |
When referencing a jbi component as a dependency of a project, its maven dependency are transitively included, which makes no sense since the jbi contains its dependency and is not meant to be added to classpath.
Change definition of jbi components to be not included in classpath and to be including their dependencies. |
When referencing a jbi component as a dependency of a project, its maven dependency are transitively included, which makes no sense since the jbi contains its dependency and is not meant to be added to classpath.
TODO: Change definition of jbi components to be not included in classpath and to be including their dependencies. TODO: Document the fact that jbi-component dependencies can's be relied upon for their dependencies. For example for POJO (which can need petals-jbi, petals-cdk-api and petals-cdk-core). |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 2.4.0 [ 10382 ] | |
| Resolution | Fixed [ 1 ] |