Yes, in the karaf-maven-plugin, change the scope of the kar, and define
the feature as bootFeatures: it won't update the startup.properties file.
Regards
JB
On 09/25/2014 10:21 AM, MarkD wrote:
Yeah, I have to reply on the nabble interface (otherwise they bounce) so I
didn't see your reply until after I'd replied to Achim.
Is there anyway around this or is it a case of waiting for this pax-wrap?
The dependency is transitive from:
<groupId>com.esotericsoftware.kryo</groupId>
<artifactId>kryo</artifactId>
so I can't change the scope.
Is there a setting on the karaf maven plugin for feature packaging, perhaps?
Thanks for the quick spot!
--
View this message in context:
http://karaf.922171.n3.nabble.com/Runtime-exception-resolving-system-bundle-with-the-wrap-protocol-Custom-distribution-tp4035504p4035511.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
