Logic behind generate-features-xml plugin?

[PJR69 <pe...@insta.fi>]

I'm trying to create a KAR-archive of my application to be deployed to Karaf
and for this I'm trying to generate the features.xml file using the
generate-features-xml plugin.

However, I'm not entirely satisfied for the features.xml-file it generates.

My project structure is roughly like this (X is my main application
project):
X-Feature
X -> Depend on A and B and 3rd party bundles (some provided, some not)
A -> Depend on B and 3rd party bundles (some provided, some not)
B -> Depend on 3rd party bundles (some provided, some not)


I would like to generate ultimately just a single feature : 'X' which has
bundles A, B and some dependencies but not all as many are provided in the
Karaf-setup (like CXF, Camel and ActiveMQ).

When I run the features.xml-file generation, I get several features and I'm
not quite sure about the logic in generating them.

I do get a feature X that has bundle A as dependendy inside the
<feature>-element and bundle B should also be inside the <feature>-element
but for some reason a feature gets generated for it. Then I get a feature
like jmockit, which we use in testing and some other features as well, which
all are just transitive dependencies.

I created the 'X-Feature' project just for creating the KAR-packaging and
the features.xml-file and it has no source code, it has basically only
dependency to bundle X on pom.xml and the generate-features-xml and
create-kar plugin executions. I'd assume that I would get ONLY feature 'X'
and dependencies as <bundle>-elements (excluding the provided ones) but that
doesn't seem to be the case.

Could you shortly explain the logic behind the generate-features-plugin? How
does it determine WHAT features it generates? For example, what could be the
reason that it generates B as a feature and not as a <bundle> inside feature
X? I don't want multiple features, only one feature.



--
View this message in context: http://karaf.922171.n3.nabble.com/Logic-behind-generate-features-xml-plugin-tp4027050.html
Sent from the Karaf - User mailing list archive at Nabble.com.

RE: Logic behind generate-features-xml plugin?

[PJR69 <pe...@insta.fi>]

Ok, I noticed that I have an issue with downstream dependencies (coming down from root-pom) which causes this issue. So no worries, I'll modify my dependencies and see if the features.xml starts to look better.


-          Petri

From: PJR69 [via Karaf] [mailto:ml-node+s922171n4027050h88@n3.nabble.com]
Sent: 11. joulukuuta 2012 7:57
To: Riipinen Petri
Subject: Logic behind generate-features-xml plugin?

I'm trying to create a KAR-archive of my application to be deployed to Karaf and for this I'm trying to generate the features.xml file using the generate-features-xml plugin.

However, I'm not entirely satisfied for the features.xml-file it generates.

My project structure is roughly like this (X is my main application project):
X-Feature
X -> Depend on A and B and 3rd party bundles (some provided, some not)
A -> Depend on B and 3rd party bundles (some provided, some not)
B -> Depend on 3rd party bundles (some provided, some not)


I would like to generate ultimately just a single feature : 'X' which has bundles A, B and some dependencies but not all as many are provided in the Karaf-setup (like CXF, Camel and ActiveMQ).

When I run the features.xml-file generation, I get several features and I'm not quite sure about the logic in generating them.

I do get a feature X that has bundle A as dependendy inside the <feature>-element and bundle B should also be inside the <feature>-element but for some reason a feature gets generated for it. Then I get a feature like jmockit, which we use in testing and some other features as well, which all are just transitive dependencies.

I created the 'X-Feature' project just for creating the KAR-packaging and the features.xml-file and it has no source code, it has basically only dependency to bundle X on pom.xml and the generate-features-xml and create-kar plugin executions. I'd assume that I would get ONLY feature 'X' and dependencies as <bundle>-elements (excluding the provided ones) but that doesn't seem to be the case.

Could you shortly explain the logic behind the generate-features-plugin? How does it determine WHAT features it generates? For example, what could be the reason that it generates B as a feature and not as a <bundle> inside feature X? I don't want multiple features, only one feature.
________________________________
If you reply to this email, your message will be added to the discussion below:
http://karaf.922171.n3.nabble.com/Logic-behind-generate-features-xml-plugin-tp4027050.html
To start a new topic under Karaf - User, email ml-node+s922171n930749h57@n3.nabble.com<ma...@n3.nabble.com>
To unsubscribe from Karaf - User, click here<http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=930749&code=cGV0cmkucmlpcGluZW5AaW5zdGEuZml8OTMwNzQ5fDU5NTY5OTMzOA==>.
NAML<http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>

________________________________
Insta lahjoittaa t?n? vuonna joulukortti- ja lahjavarat sotaveteraanien hyv?ksi. Rauhallista Joulua ja Onnellista Uutta Vuotta 2013!

____________________________________________________________________________________________

Instead of sending Christmas Cards and gifts, Insta has made a contribution to veterans' recreational activities. Best wishes for a peaceful Christmas and a Happy New Year 2013!




--
View this message in context: http://karaf.922171.n3.nabble.com/Logic-behind-generate-features-xml-plugin-tp4027050p4027051.html
Sent from the Karaf - User mailing list archive at Nabble.com.