On 23/05/2020 3:19 pm, Paul Fraser wrote:
JB,
But it works when installed in the deplo folder.
There is something different when deployed from the deploy folder and when it is cllaed with the
feature service.
== PLEASE IGNORE...The following is rubbish is Rubbish
==
Thanks JB,
Will do some more investigation.
Paul
On 23/05/2020 3:59 pm, Jean-Baptiste Onofre wrote:
And by the way: I never use the deploy folder, so yes, all is install via
service using URL.
I really think your issue is about mvn/url resolution.
Regards
JB
Le 23 mai 2020 à 07:48, Paul F
And by the way: I never use the deploy folder, so yes, all is install via
service using URL.
I really think your issue is about mvn/url resolution.
Regards
JB
> Le 23 mai 2020 à 07:48, Paul Fraser a écrit :
>
> JB,
>
> Inline.
>
> On 23/05/2020 3:26 pm, Jean-Baptiste Onofre wrote:
>> The di
On a fresh Karaf 4.2.8:
karaf@root()> kar:install
mvn:org.apache.karaf.examples/karaf-maven-example-kar/4.2.8/kar
karaf@root()> kar:list
KAR Name
───
karaf-maven-example-kar
It seems to work fine.
Now, another test:
karaf@root()> kar:install file:/Users/jbonofre/test.kar
ka
JB,
Inline.
On 23/05/2020 3:26 pm, Jean-Baptiste Onofre wrote:
The difference is in the resolution.
When you use the deploy folder: when you drop the kar in the deploy folder,
it’s directly resolved from there. That’s the difference.
Same when you do feature:install webconsole: webconsole is
The difference is in the resolution.
When you use the deploy folder: when you drop the kar in the deploy folder,
it’s directly resolved from there. That’s the difference.
Same when you do feature:install webconsole: webconsole is not part of karaf
standard distribution, so it’s not in the syste
JB,
But it works when installed in the deplo folder.
There is something different when deployed from the deploy folder and when it is cllaed with the
feature service.
I get the same problem if I try featureService.install("web-console")
Paul
On 23/05/2020 3:13 pm, Jean-Baptiste Onofre wrote
The piece of code you mention in the FeatureService is about the provisioning,
so resolution/download of the artifact.
Maybe your features XML contained in the Kar contains "bad" URL ? Do you use
only mvn URL in the features XML packaged in the KAR (no file URL for instance)
?
Don’t you have s
JB,
The kar file is being exploded OK and the system bogs down when resolving the
contained features.
Paul
On 23/05/2020 3:03 pm, Paul Fraser wrote:
JB,
Did you see my second email which indicates the problem in in the Feature
Service?
Paul
On 23/05/2020 3:01 pm, Jean-Baptiste Onofre wrote
JB,
Did you see my second email which indicates the problem in in the Feature
Service?
Paul
On 23/05/2020 3:01 pm, Jean-Baptiste Onofre wrote:
If nothing happen, I bet it’s the URL resolution download.
If the kar file is large, it can take time to download as Karaf is "caching"
the Kar file.
If nothing happen, I bet it’s the URL resolution download.
If the kar file is large, it can take time to download as Karaf is "caching"
the Kar file.
Did you wait long ? Maybe a thread dump would help.
Regards
JB
> Le 23 mai 2020 à 06:56, Paul Fraser a écrit :
>
> JB,
>
> More information i
JB,
More information in my follow up mail.
Comments inline.
On 23/05/2020 2:24 pm, Jean-Baptiste Onofre wrote:
Hi,
Can you describe a bit the problem ?
Does the path is a valid URL (file, http, mvn) to the Kar file ?
The exact same kar file works when added to deploy folder so I do not think
Hi,
Can you describe a bit the problem ?
Does the path is a valid URL (file, http, mvn) to the Kar file ?
Kar:install command (and the service) are part of the itest, so they work at
least here.
Maybe you are on Windows platform ?
Regards
JB
> Le 22 mai 2020 à 13:28, Paul Fraser a écrit :
>
Hi,
V 4.2.8
The problem is occuring when the future does not return and no error is thrown
in this code-
https://github.com/apache/karaf/blob/262343a5f60b29967a3c72a198f6427b5a6bf5e9/features/core/src/main/java/org/apache/karaf/features/internal/service/FeaturesServiceImpl.java#L967
The system
Of the top of my head it is kar:install File://path.to.kar.file.kar
After kar: do a tab for auto completion and display all options.
-
if ( you want ) { you can } else { you can't }
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
Hi,
Using
karService#install(karPath.toUri) fails
but copying the kar jar into the deploy folder works.
Can anyone with an inner knowledge of both approaches offer any advice as to possible cause of the
failure of the karService in this case?
Or suggest where I should be looking to find
16 matches
Mail list logo
