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

Ascending order - Click to sort in descending order
Victor NOËL made changes - Fri, 16 Jan 2015 - 09:52:33 +0100
Field Original Value New Value
Assignee Christophe DENEUX [ cdeneux ] Victor NOËL [ vnoel ]
Victor NOËL made changes - Fri, 16 Jan 2015 - 09:54:31 +0100
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Victor NOËL made changes - Fri, 16 Jan 2015 - 16:27:17 +0100
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).
Victor NOËL made changes - Mon, 19 Jan 2015 - 15:28:25 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Victor NOËL added a comment - Mon, 26 Jan 2015 - 16:15:08 +0100
  • jbi-component, jbi-service-unit, jbi-service-assembly and jbi-shared-library dependency types do not bring their dependencies anymore with them (used for example in integration tests).
  • zip dependency type still bring its dependencies with it (used for example in the distribution artefact).
  • the documentation of the SE POJO was updated to give the name of the dependencies providing some classes needed to implement SUs.
  • the use cases documentation of the SE JSR181 was updated to give the name of the dependencies providing some classes needed to implement SUs.
Show
Victor NOËL added a comment - Mon, 26 Jan 2015 - 16:15:08 +0100
  • jbi-component, jbi-service-unit, jbi-service-assembly and jbi-shared-library dependency types do not bring their dependencies anymore with them (used for example in integration tests).
  • zip dependency type still bring its dependencies with it (used for example in the distribution artefact).
  • the documentation of the SE POJO was updated to give the name of the dependencies providing some classes needed to implement SUs.
  • the use cases documentation of the SE JSR181 was updated to give the name of the dependencies providing some classes needed to implement SUs.
Victor NOËL made changes - Mon, 26 Jan 2015 - 16:15:08 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 2.4.0 [ 10382 ]
Resolution Fixed [ 1 ]
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
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.