[
https://issues.apache.org/jira/browse/KARAF-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149178#comment-14149178
]
Stuart McCulloch commented on KARAF-2961:
-----------------------------------------
Seriously? We have a sizeable number of plugin-style builds and expect
customers to write their own plugins. IMHO forcing them all to add copies of
the same template feature file to each plugin build is unreasonable when adding
support for this is trivial and doesn't affect anyone else (as it's controlled
by a simple flag).
If this small improvement really is never going to be accepted then we'll have
to maintain our own version of the plugin because we're using template feature
files at the moment as a workaround and it doesn't scale as a solution.
> When a feature is generated from a bundle project, include that bundle in the
> feature
> -------------------------------------------------------------------------------------
>
> Key: KARAF-2961
> URL: https://issues.apache.org/jira/browse/KARAF-2961
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-tooling
> Reporter: Stuart McCulloch
> Assignee: Jean-Baptiste Onofré
>
> We're migrating a custom plugin framework over to Karaf and would like to
> both create the OSGi bundle and generate the associated Karaf feature in the
> same Maven project. Otherwise downstream clients will need to create two
> Maven projects for each plugin: one to create the bundle, and one to create
> the Karaf feature.
> The proposed change is to consider the project packaging, and if it is
> "bundle" then include the main project artifact (ie. the bundle itself) in
> the generated feature. This requires no configuration change and should not
> affect anyone generating features in isolation. We could also add a new flag
> such as "includeProjectArtifact" so this change has to be explicitly enabled,
> if people prefer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
