camel.cloud.KuraCloudComponent.createEndpoint(KuraCloudComponent.java:74)
at
org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:114)
at
org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:568)
---
Any help debugging or understand this would be great.
T
Hi,
There seems to be a goal for maven "karaf:run" which can run a single
bundle. But is there some way to run a karaf assembly, directly from maven.
Thanks for your help
Jens
--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbru
Cool, a link to that would really help!
On Wed, Sep 14, 2016 at 12:01 PM, Jean-Baptiste Onofré
wrote:
> Hi Jens
>
> Run can run a complete karaf distribution (I blogged about it, let me find
> it out).
>
> Regards
> JB
> On Sep 14, 2016, at 11:18, Jens Reimann wrot
Is your goal to start one up and then run tests against it? If so, I have
> some other suggestions.
>
> On Wed, Sep 14, 2016 at 5:17 AM, Jens Reimann wrote:
>
>> Hi,
>>
>> There seems to be a goal for maven "karaf:run" which can run a single
>> bund
> Pax exam will run karaf and be setup to include your custom features. It
> is how I do integration testing
>
> On Sep 14, 2016 5:18 AM, "Jens Reimann" wrote:
>
>> Hi,
>>
>> There seems to be a goal for maven "karaf:run" which can run a singl
t 6:48 AM, Benson Margulies
> wrote:
>
>> Is your goal to start one up and then run tests against it? If so, I have
>> some other suggestions.
>>
>> On Wed, Sep 14, 2016 at 5:17 AM, Jens Reimann
>> wrote:
>>
>>> Hi,
>>>
>>> The
, Achim Nierbeck
wrote:
> call karaf debug and attach eclipse to the opened port is an alternative
>
> 2016-09-14 13:57 GMT+02:00 Jens Reimann :
>
>> Yes, that is then not executed by the Eclipse maven runner .. just a
>> shell script. So debugging will not be set up.
>>
:30 PM, Benson Margulies
wrote:
> Run the exec-maven-plugin to run the 'karaf debug' command if you can't
> configure eclipse to just run a shell command.
>
>
> On Wed, Sep 14, 2016 at 8:16 AM, Jens Reimann wrote:
>
>> Sure, that could be workaround. If
fork a new java process. So launching maven with
>>> debugging won't give you debugging inside of Karaf.
>>>
>>>
>>> On Wed, Sep 14, 2016 at 8:42 AM, Jens Reimann
>>> wrote:
>>>
>>>> Well that defies the purpose of starting
31a1a4216d
> e9d232f211/camel-core/src/main/java/org/apache/camel/
> impl/CompositeRegistry.java#L79
> [3] https://github.com/apache/camel/blob/master/components/
> camel-core-osgi/src/main/java/org/apache/camel/core/osgi/
> OsgiServiceRegistry.java
> [4] https://github.com/apache/came
NSATISFIED | org.eclipse.kura.ssl.SslManagerService
In the "webconsole" they don't even show up.
Looking at the log with "log:display" doesn't show any errors. A few other
services in the same bundle are activated though.
Thanks for any help.
Jens
--
Jens Reimann
Senior
gt; When I had this it was because a configuration was required, but not
> available.
>
> On 5 Oct 2016, at 11:02, Jens Reimann wrote:
>
> Hi,
>
> I am currently having troubles with a few declarative services. Listing
> them with "scr:components" sh
> JB
>
> On 10/05/2016 03:26 PM, David Jencks wrote:
>
>> The scr command from felix ds does and has for quite a while.
>>
>> david jencks
>>
>> On Oct 5, 2016, at 4:32 AM, Jens Reimann >> <mailto:jreim...@redhat.com>> wrote:
>>>
>
I haven't found a way to do the same with the
"assembly-property-edits.xml" concept. Most of my property edits stay the
same between the different child bundles, only a few have to be modified.
Thank for your help
Jens
--
Jens Reimann
Senior Software Engineer / EMEA ENG Middlewar
//maven.apache.org/pom.html#Plugins
> Best regards,
> Markus
>
--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
_
Red
this,
> yet.
>
> Best regards,
> Markus
>
--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
_
Red Hat GmbH,
...
> The assembly-property-edits is more limited imho.
>
> 2016-10-06 15:29 GMT+02:00 Jens Reimann :
>
>> Hi,
>>
>> I am currently building several Apache Karaf distributions and would like
>> to use a modular Maven build for that.
>>
>> It is possible
profiles ?
>>> You can extend / combine / override stuff, inherit from multiple
>>> parents, etc...
>>> The assembly-property-edits is more limited imho.
>>>
>>> 2016-10-06 15:29 GMT+02:00 Jens Reimann :
>>>
>>>> Hi,
>>>>
>
the whole set of configuration files.
>
> Let me know if you have any problem if you investigate this.
>
> Guillaume
>
> 2016-10-12 18:51 GMT+02:00 Jens Reimann :
>
>> Ok, sorry.
>>
>> Do you have a suggestion how to edit properties files in a different way?
>
Having a look at a possible candidate for this (org.apache.felix :
org.apache.felix.scr.annotations : 1.11.0) I find that this bundle is not a
bundle and has no OSGi metadata.
I am probably doing something wrong. But what is it?
Thanks for your help
Cheers
Jens
--
Jens Reimann
Senior Software Eng
l the scr feature.
>
> Christian
>
> On 17.10.2016 15:05, Jens Reimann wrote:
>
> Hi,
>
> using the SCR annotations and trying perform "mvn verify" on a feature
> referencing this bundle results in the following resolution error:
>
> ---
> osgi.wiring
stood it the annotations should not be imported.
>>
>> Yes, there is no need to import the component service annotations.
>> As already written, this annotations are used a compile time to
>> generate the XML files for DS.
>>
>> Best regards,
>> Markus
>&g
This may be a "noob" question, but to me it looks like that in the karaf
log file and this "log:display" command all exception are missing the
"cause" stack traces.
Is there a way to enable this. Google did not turn up anything useful.
Thanks
Jens
--
Jens Re
n 10/19/2016 09:59 AM, Jens Reimann wrote:
>
>> This may be a "noob" question, but to me it looks like that in the karaf
>> log file and this "log:display" command all exception are missing the
>> "cause" stack traces.
>>
>> Is there a
Thanks! That should help at least for shell commands.
On Wed, Oct 19, 2016 at 11:11 AM, Jean-Baptiste Onofré
wrote:
> It's a command.
>
> Regards
> JB
>
> On 10/19/2016 11:09 AM, Jens Reimann wrote:
>
>> Thanks for the help. Is this a command? Or a configuration
/camel-milo/milo-0.1.0-SNAPSHOT.kar
Unless I did something wrong, it seems there is an issue with "kar:install"
and redirects?!
Cheers
Jens
--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89
or resource (like a bundle) ?
>
> Regards
> JB
>
> On 10/20/2016 12:27 PM, Jens Reimann wrote:
>
>> I just tried to install a KAR using:
>>
>> kar:install http://dentrassi.de/camel-milo/milo-0.1.0-SNAPSHOT.kar
>>
>> That looked like it went fine. R
the dependency above causes Karaf to always complain
that version 1.1.1 is not available even though version 1.0.2 is available.
Declaring a version range "[1,2)" for Paho makes it complain that an upper
version cannot be evaluated.
Any ideas?
Thanks for your help
Jens
--
Jens Reim
apache.karaf.features/standard/${karaf.version}/xml/features
The full maven POM is here: http://pastebin.com/VtiWJRuA
Thanks
Jens
--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Ge
29 matches
Mail list logo
