[ 
https://issues.apache.org/jira/browse/ARIES-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Bosschaert resolved ARIES-1490.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: esa-maven-plugin-1.0.0

Many thanks for the patch, [~tom.dewolf]! It's applied in 
https://svn.apache.org/viewvc?view=revision&revision=1785159

> 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
>            Assignee: David Bosschaert
>             Fix For: esa-maven-plugin-1.0.0
>
>
> 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.15#6346)

Reply via email to