[
https://issues.apache.org/jira/browse/ARIES-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15158534#comment-15158534
]
Tom De Wolf commented on ARIES-1490:
------------------------------------
Yes, your understanding is correct. We do not want to list all dependencies
individually and thus rely on the fact that the esa plugin uses the maven
dependency tree to include the transitive dependencies.
However, for us they are actual content of the esa subsystem so we would like
to mark them as such by including them in the Subsystem-Content header without
having to list them again. To structure a big project we also like to use
external pom.xml files including a list of dependencies and having the esa
plugin able to cope with that would easy the use of the plugin for bigger
projects too.
Also being able to influence the start order is sometimes needed.
It is very confusing that the content specified in the header is out of sync
with the content that is actually in the esa. Why make the difference? What
would be wrong to at least add all bundles included in the esa archive also to
the manifest Subsystem-Content header? Sounds more consistent.
> 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)
