Hi Jean-Baptiste,
as I said, the main reason for using the 3.x branch is that it allows me
to exclude transitive dependencies: the
includeTransitiveDependency flag. See
https://issues.apache.org/jira/browse/KARAF-931
Maybe that flag can be back-ported to the features-maven-pluing in the
2.x branches?
best regards, Peter
On 08/21/2012 04:30 PM, Jean-Baptiste Onofré wrote:
Correct,
the XSD have changed between 2.2.x/2.3.x and 3.0.0. The 3.0.0 branch
contains new attributes which are not supported by 2.2.x/2.3.x branches.
However, most of the karaf-maven-plugin features are available in the
features-maven-plugin of 2.2.x/2.3.x branches.
Which are the issues that you have that "force" you to use 3.0.0 ?
Thanks,
Regards
JB
On 08/21/2012 10:41 AM, peter.gardfjall.work wrote:
Hi all,
I'm using the karaf-maven-plugin
(org.apache.karaf.tooling:karaf-maven-plugin:3.0.0-SNAPSHOT) to generate
feature descriptors and kar files.
Note that although I am _running_ these features on a 2.2.9 version of
Karaf, I'm using the 3.0.0-SNAPSHOT to _generate_ the features, the main
reason being that the plugin on the 3.0.0 branch has some nice features
(such as being able to exclude transitive dependencies -- the
includeTransitiveDependency flag).
If I am correct, a recent commit on the 3.0.0 branch has resulted in the
karaf-maven-plugin now producing feature descriptors with a new
namespace ( http://karaf.apache.org/xmlns/features/v1.1.0 instead of
http://karaf.apache.org/xmlns/features/v1.0.0), which effectively makes
the generated features incompatible with the 2.2.9 version of Karaf.
Is this correct?
If so, what can be done to remedy the situation?
best regards, Peter
