Hi Stephen,

I played around with KAR’s for quite a while with similar issues. I ended up 
ditching them in favour of the karaf feature deployment. This is far simpler 
and cleaner than kar. It does require that you have your dependencies / bundles 
available in an accessible maven repo from your deployment environment or in 
the karaf system folder using the maven layout.

Re your assumption around prod like deployments, I would agree that is a 
correct assumption. However, if you can’t get the kar working try the route 
above, it’s what I ended up having to do.

Cheers,
Matt.

From: Stephen Munro [mailto:stephen.ross.mu...@gmail.com]
Sent: Saturday, 7 October 2017 5:36 AM
To: user@karaf.apache.org
Subject: Fwd: KAR deployment


I'm having a small problem constructing a KAR file. Basically, I have a pom 
with the type set to KAR. The maven plugin generates a KAR file, which contains 
some of the libraries, specifically my OSGI bundles and their dependencies.
The problem is that the requirements specified in the feature file i.e 
<feature>cxf-jaxrs</feature> are not pulled into the KAR file.
I assumed that the KAR file was meant to be a self contained deployment 
artifact with no requirement to fetch additional dependencies, thus making it 
suitable for production environments where network access is restricted. Is 
this assumption incorrect.
As a side note, I attempted to use the karaf assembly task. I've found the 
documentation on this goal to be extremely scarce and I've not managed to find 
any examples which use this particular goal. When attempting to learn/use it, I 
was hit with many null pointer exceptions, leading me to believe that the 
assembly goal is buggy. Can someone confirm the status of this and/or 
demonstrate a working example?


--
Warmest Regards,

Stephen Munro



--
Warmest Regards,

Stephen Munro

This email, including any attachments sent with it, is confidential and for the 
sole use of the intended recipient(s). This confidentiality is not waived or 
lost, if you receive it and you are not the intended recipient(s), or if it is 
transmitted/received in error.

Any unauthorised use, alteration, disclosure, distribution or review of this 
email is strictly prohibited. The information contained in this email, 
including any attachment sent with it, may be subject to a statutory duty of 
confidentiality if it relates to health service matters.

If you are not the intended recipient(s), or if you have received this email in 
error, you are asked to immediately notify the sender. You should also delete 
this email, and any copies, from your computer system network and destroy any 
hard copies produced.

If not an intended recipient of this email, you must not copy, distribute or 
take any action(s) that relies on it; any form of disclosure, modification, 
distribution and/or publication of this email is also prohibited.

Although the Queensland Ambulance Service takes all reasonable steps to ensure 
this email does not contain malicious software, the Queensland Ambulance 
Service does not accept responsibility for the consequences if any person's 
computer inadvertently suffers any disruption to services, loss of information, 
harm or is infected with a virus, other malicious computer programme or code 
that may occur as a consequence of receiving this email.

Unless stated otherwise, this email represents only the views of the sender and 
not the views of the Queensland Government.

********************************************************************************

The content presented in this publication is distributed by the Queensland 
Government as an information source only. The State of Queensland makes no 
statements, representations or warranties about the accuracy, completeness or 
reliability of any information contained in this publication. The State of 
Queensland disclaims all responsibility and all liability (including without 
limitation for liability in negligence) for all expenses, losses, damages and 
costs you might incur as a result of the information being inaccurate or 
incomplete in any way, and for any reason reliance was placed on such 
information.

Reply via email to