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

Stuart McCulloch commented on KARAF-2961:
-----------------------------------------

PS. when cherry-picking the fix back to 3.0.x the control.xml in the IT needs a 
slight adjustment to match the expected prelude:
{code}
diff --git 
a/tooling/karaf-maven-plugin/src/it/test-include-project-artifact/control.xml 
b/tooling/karaf-maven-plugin/src/it/test-include-project-artifact/control.xml
index d4db328..c030079 100644
--- 
a/tooling/karaf-maven-plugin/src/it/test-include-project-artifact/control.xml
+++ 
b/tooling/karaf-maven-plugin/src/it/test-include-project-artifact/control.xml
@@ -18,8 +18,8 @@
   ~ under the License.
   -->
 
-<features xmlns="http://karaf.apache.org/xmlns/features/v1.3.0"; 
name="test-include-project-artifact">
-    <feature name="test-include-project-artifact" 
description="test-include-project-artifact" version="1.0.0.SNAPSHOT">
+<features xmlns="http://karaf.apache.org/xmlns/features/v1.2.1"; 
name="test-include-project-artifact">
+    <feature name="test-include-project-artifact" 
description="test-include-project-artifact" version="1.0-SNAPSHOT">
         <bundle>mvn:test/test-include-project-artifact/1.0-SNAPSHOT</bundle>
     </feature>
 </features>
{code}

> 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é
>             Fix For: 4.0.0, 3.0.2
>
>
> 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)

Reply via email to