Maven Petals Plugin

Do not include dependencies of jbi components in the maven dependency resolution

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.3.0
  • Fix Version/s: 2.4.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    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).

    Show
    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).
  • Environment:
    -

Activity

Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
2m 5s
1
Victor NOËL
Fri, 16 Jan 2015 - 09:54:31 +0100
Open Open In Progress In Progress
3d 5h 33m
1
Victor NOËL
Mon, 19 Jan 2015 - 15:28:25 +0100
In Progress In Progress Resolved Resolved
7d 46m
1
Victor NOËL
Mon, 26 Jan 2015 - 16:15:08 +0100

People

Dates

  • Created:
    Fri, 16 Jan 2015 - 09:52:26 +0100
    Updated:
    Mon, 26 Jan 2015 - 16:15:08 +0100
    Resolved:
    Mon, 26 Jan 2015 - 16:15:07 +0100