You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Andrei Pozolotin <an...@gmail.com> on 2013/02/10 02:34:29 UTC
features missing from features
*Hello there.*
I miss the following features in features - see link and below
https://gist.github.com/carrot-garden/4747691
### 1. build feature for a bundle
### 2. depend on a feature.xml
### 3. depend on a feature with repository
I am curious is it just me missing this or more people need this? :-)
Thank you,
Andrei
########################################################
## features missing in features
### 1. build feature for a bundle
example: pom-A.xml
currently there is no way build both bundle.jar and feature.xml in one step:
karaf-maven-plugin is including all scopes, so resulting feature.xml is useless.
workaround: duplicate efforts and setup separate project
just to produce feature.xml for the same bundle.jar
solution: fix bugs in karaf-maven-plugin
### 2. depend on a feature.xml
example: pom-A.xml pom-B.xml pom-C.xml
currently there is no way to depend on feature.xml in maven for a bundle.jar
this is because feature.xml is resolved via peer pom.xml for dependency purposes
with result being: pom-A.xml classes are available, pom-B.xml are missing in the pom-C.xml project
workaround: duplicate efforts / introduce hacks and have pom-B.xml reference itself as dependency
solution: add life cycle mapping for karaf-maven-plugin, so it will
automatically add pom-B.xml artifact module-B.jar on class path when it finds feature-B.xml
### 3. depend on a feature with repository
this is similar to previous, except repositories from features are also resolved in maven
########################################################
Re: features missing from features
Posted by Andrei Pozolotin <an...@gmail.com>.
*Andreas*
thank you for your support. please comment/review:
https://issues.apache.org/jira/browse/KARAF-1972
https://github.com/apache/karaf/pull/11
Thank you,
Andrei
-------- Original Message --------
Subject: Re: features missing from features
From: Andreas Pieber <an...@gmail.com>
To: Apache Karaf <us...@karaf.apache.org>
Date: Sun 10 Feb 2013 12:04:05 AM CST
> From my point of view I see no problem with those three points.
> Solutions for them could definitely help people with writing their
> features.
>
> So, solving those three would definitely have my support.
>
> Kind regards,
> Andreas
>
>
> On Sun, Feb 10, 2013 at 2:34 AM, Andrei Pozolotin
> <andrei.pozolotin@gmail.com <ma...@gmail.com>> wrote:
>
> *Hello there.*
>
> I miss the following features in features - see link and below
> https://gist.github.com/carrot-garden/4747691
>
> ### 1. build feature for a bundle
>
> ### 2. depend on a feature.xml
>
> ### 3. depend on a feature with repository
>
> I am curious is it just me missing this or more people need
> this? :-)
>
> Thank you,
>
> Andrei
>
> ########################################################
>
> ## features missing in features
>
> ### 1. build feature for a bundle
>
> example: pom-A.xml
>
> currently there is no way build both bundle.jar and feature.xml in one step:
> karaf-maven-plugin is including all scopes, so resulting feature.xml is useless.
>
> workaround: duplicate efforts and setup separate project
> just to produce feature.xml for the same bundle.jar
>
> solution: fix bugs in karaf-maven-plugin
>
> ### 2. depend on a feature.xml
>
> example: pom-A.xml pom-B.xml pom-C.xml
>
> currently there is no way to depend on feature.xml in maven for a bundle.jar
>
> this is because feature.xml is resolved via peer pom.xml for dependency purposes
> with result being: pom-A.xml classes are available, pom-B.xml are missing in the pom-C.xml project
>
> workaround: duplicate efforts / introduce hacks and have pom-B.xml reference itself as dependency
>
> solution: add life cycle mapping for karaf-maven-plugin, so it will
> automatically add pom-B.xml artifact module-B.jar on class path when it finds feature-B.xml
>
> ### 3. depend on a feature with repository
>
> this is similar to previous, except repositories from features are also resolved in maven
>
> ########################################################
>
>
Re: features missing from features
Posted by Andreas Pieber <an...@gmail.com>.
>From my point of view I see no problem with those three points. Solutions
for them could definitely help people with writing their features.
So, solving those three would definitely have my support.
Kind regards,
Andreas
On Sun, Feb 10, 2013 at 2:34 AM, Andrei Pozolotin <
andrei.pozolotin@gmail.com> wrote:
> *Hello there.*
>
> I miss the following features in features - see link and below
> https://gist.github.com/carrot-garden/4747691
>
> ### 1. build feature for a bundle
>
> ### 2. depend on a feature.xml
>
> ### 3. depend on a feature with repository
>
> I am curious is it just me missing this or more people need this? :-)
>
> Thank you,
>
> Andrei
>
> ########################################################
>
> ## features missing in features
>
> ### 1. build feature for a bundle
>
> example: pom-A.xml
>
> currently there is no way build both bundle.jar and feature.xml in one step:
> karaf-maven-plugin is including all scopes, so resulting feature.xml is useless.
>
> workaround: duplicate efforts and setup separate project
> just to produce feature.xml for the same bundle.jar
>
> solution: fix bugs in karaf-maven-plugin
>
> ### 2. depend on a feature.xml
>
> example: pom-A.xml pom-B.xml pom-C.xml
>
> currently there is no way to depend on feature.xml in maven for a bundle.jar
>
> this is because feature.xml is resolved via peer pom.xml for dependency purposes
> with result being: pom-A.xml classes are available, pom-B.xml are missing in the pom-C.xml project
>
> workaround: duplicate efforts / introduce hacks and have pom-B.xml reference itself as dependency
>
> solution: add life cycle mapping for karaf-maven-plugin, so it will
> automatically add pom-B.xml artifact module-B.jar on class path when it finds feature-B.xml
>
> ### 3. depend on a feature with repository
>
> this is similar to previous, except repositories from features are also resolved in maven
>
> ########################################################
>
>
>