You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Tom De Wolf (JIRA)" <ji...@apache.org> on 2016/02/21 20:28:18 UTC

[jira] [Commented] (ARIES-1490) The esa maven plugin provides more flexibility when creating the subsystem manifest

    [ https://issues.apache.org/jira/browse/ARIES-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156180#comment-15156180 ] 

Tom De Wolf commented on ARIES-1490:
------------------------------------

[~jwross@us.ibm.com] [~bosschaert] any chance this is getting resolved? It even seems to be a bug in the esa-maven-plugin as that plugin provides an option to include transitive dependencies as jars within the esa file BUT it does not list those transitive dependencies in the SUBSYSTEM.MF manifest as content of the esa. So a mismatch between what is put in the esa archive and what is listed in the manifest as content which is incorrect.

> The esa maven plugin provides more flexibility when creating the subsystem manifest
> -----------------------------------------------------------------------------------
>
>                 Key: ARIES-1490
>                 URL: https://issues.apache.org/jira/browse/ARIES-1490
>             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
(v6.3.4#6332)