aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Ross (JIRA)" <>
Subject [jira] [Commented] (ARIES-1490) The esa maven plugin provides more flexibility when creating the subsystem manifest
Date Mon, 22 Feb 2016 12:45:18 GMT


John Ross commented on ARIES-1490:

I don't participate in the esa-maven-plugin development but strongly suspect this is intentional.
The specification allows dependencies as well as content to be packaged in an ESA. The dependencies
will then become part of the local repository and provisioned from there. If you want everything
in an ESA to automatically be considered content, you may simply not specify the Subsystem-Content

> The esa maven plugin provides more flexibility when creating the subsystem manifest
> -----------------------------------------------------------------------------------
>                 Key: ARIES-1490
>                 URL:
>             Project: Aries
>          Issue Type: New Feature
>          Components: ESA Maven Plugin
>    Affects Versions: esa-maven-plugin-1.0.0
>            Reporter: Wouter Bancken
> When determining which dependencies are included in the archive, the ESA maven plugin
provides different possibilities as to which dependencies are included (transitive dependencies
vs only direct dependencies). 
> When generating the subsystem manifest, the plugin always decides to only list the direct
dependencies and therefore it does not include the transitive dependencies as part of the
subsystem content even though they are present in the archive.
> Additionally, the type of the dependencies (e.g. 'pom') is not taken into account. This
makes it impossible to extract a sequence of related dependencies into a separate pom file
to improve the overall readability. The readability would improve greatly if a related set
of dependencies could be imported from another pom.

This message was sent by Atlassian JIRA

View raw message