[
https://issues.apache.org/jira/browse/ARIES-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157082#comment-15157082
]
John Ross commented on ARIES-1490:
----------------------------------
If I understand correctly, your scenario is that you start with some content
that you know a priori. The tooling then goes out and locates all dependencies.
Furthermore, it gives you the option of packaging those dependences in the ESA.
This would be the typical case in my mind. In addition, you want an option to
also have those dependencies included as content by adding them to the
Subsystem-Content header. May I ask why? Dependencies will always be started
before content; however, there is no way to specify a start order among the
dependencies themselves. Is that why you want them as content?
> 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)
