to resolve FOO/0.0.1: missing requirement [FOO/0.0.1]
> >> osgi.wiring.package;
> >>
>
> filter:="(&(osgi.wiring.package=org.osgi.service.component)(version>=1.3.0)(!(version>=2.0.0)))”]]
> >
> > This error is actually not to do with annotatio
Karaf, but there
> are issues in Karaf if you end up with two DS implementations running at
> the same time (and there really should be one deployed by default!).
>
> I hope this helps.
>
> Tim
>
> Sent from my iPhone
>
> On 17 Dec 2019, at 17:51, Massimo Bono wrote:
ot;; resolution:=mandatory [caused by: Unable to
> resolve FOO/0.0.1: missing requirement [FOO/0.0.1] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=org.osgi.service.component)(version>=1.3.0)(!(version>=2.0.0)))”]]
>
>
> This error is actually not to do with annotation inheri
>=2.0.0)))"]]
Note that I install the artifact exposing class AbstractBundle via a karaf
feature.
Am I doing something which is invalid?
Thanks for any kind reply
--
*Ing. Massimo Bono*
Thanks, really appreciating it!
Il giorno mer 11 dic 2019 alle ore 20:12 ha scritto:
> It's fine. Let me check if I can improve a bit the descriptor handling.
>
> Regards
> JB
>
> Le 11 déc. 2019 10:59, Massimo Bono a écrit :
>
> ATM no, but in the future probab
> That's the way OBR works unfortunately. You can split the artifacts in
> different repositories.
>
> Do you have a lot of artifacts in your repository ?
>
> Regards
> JB
>
> Le 11 déc. 2019 09:43, Massimo Bono a écrit :
>
> Hi, now the http url works. Howeve
Sorry, I put the wrong link. The correct one is
http://karaf.922171.n3.nabble.com/Bug-on-cave-repository-update-td4056780.html
Il giorno mer 11 dic 2019 alle ore 18:43 Massimo Bono <
massimobo...@gmail.com> ha scritto:
> Hi, now the http url works. However, I'm getting the
me artifact are appended in the
repository.xml file, making the file bigger and bigger. This in turn make
obr:deploy fail. Is there a workaround?
Il giorno mer 11 dic 2019 alle ore 17:20 Massimo Bono <
massimobo...@gmail.com> ha scritto:
> yes, I'm using Cave 4.2.0. Let me try 4.2.1
> 4.2.1 ? I fixed issues on the repository location.
>
> Regards
> JB
>
> On 11/12/2019 16:07, Massimo Bono wrote:
> > Hi JB,
> >
> > here's the steps:
> > 1) I've created the repository with "cave:repository-create foo";
> > 2) I ch
id you generate the descriptor with the command first:
>
> cave:repository-update-bundle-descriptor foo
>
> ?
>
> By the way, the cave feature doesn't exist, it's just cave-repository.
> Did you clean you Karaf instance (data folder) if you migrated from a
> previou
if I query the same http url with "get", I obtain a 404 error.
Am I doing something wrong?
Thanks for any kind reply
--
*Ing. Massimo Bono*
t;
> In the test, you can check with web:list and http:list if the status is
> deployed (and not deploying).
> Maybe you test the connection before the endpoint is actually started.
> You can see how we do it in the karaf examples itests.
>
> Regards
> JB
>
> Le 16 nov
sed" (in the browser I cannot see anything as well).
Surely I'm doing something wrong. Is this the correct way to test a webapp?
Thanks for any kind reply!
--
*Ing. Massimo Bono*
refactoring:
>
> https://github.com/apache/karaf-cave/pull/27
>
> I plan to merge the PR later today and cut Cave 4.2.0 soon (probably
> during the weekend).
>
> Cave will be simpler, first Maven focus, and the repository.xml
> generation will only use local artifacts.
>
&g
* the repository.xml" (enphasis mine).
However, cave:repository-update will fail if the file is deleted from the
filesystem, hence the workaround.
Finally, my setup:
OBR SERVER:
Operating system: Raspian buster 10
Apache karaf hosting cave: 4.2.6
Apache cave: 4.1.2
OBR CLIENT:
Apache karaf wh
ries/good
>
> It's where you will have the repository.xml with the metadata.
>
> Regards
> JB
>
> Le 9 sept. 2019 14:07, Massimo Bono a écrit :
>
> Hi all,
>
> I've successfully setup in a local Docker container an instance of
> karaf ca
Hi all,
Do you any update regarding this question?
Thanks
Il giorno lun 9 set 2019 alle ore 23:07 Massimo Bono
ha scritto:
> Hi all,
>
> I've successfully setup in a local Docker container an instance of karaf
> cave with an OBR repository and I have populate it with some b
:add-url? Inside a
configuration file? I think it would be better inside a configuration file,
but I'm unsure about which one.
Sorry for the newbie question and thank for any kind reply.
--
*Ing. Massimo Bono*
ot the best solution, but works.
Il giorno mar 20 nov 2018 alle ore 11:34 Massimo Bono <
massimobo...@gmail.com> ha scritto:
> Hello,
>
> I want to test an OSGi bundle built with bnd using conditional-packages
> via pax-exam. The conditional-package allows the bundle to use some ut
Hello,
I want to test an OSGi bundle built with bnd using conditional-packages via
pax-exam. The conditional-package allows the bundle to use some utility
classes (e.g., like from https://stackoverflow.com/a/39500621/1887602)
The test is setup like the following:
@Test
public void exampleTest()
where
> it
> simply didn't have enough TLC, but at the same time It made be question how
> useful the instruction was.
>
>
>
> --
> Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
>
--
*Ing. Massimo Bono*
irectly.
> 2. It's related to the features XML generated: if the inner feature
> contains the prerequesite=true and dependency=true flags.
>
> Regards
> JB
>
> On 11/13/2017 09:50 AM, Massimo Bono wrote:
>
>> Hello,
>>
>> I've several questions about Ka
tion and thanks for any kind reply
[1]
https://stackoverflow.com/questions/24640515/how-deploy-a-war-web-project-in-karaf-3
[2] https://karaf.apache.org/manual/latest/webcontainer
--
*Ing. Massimo Bono*
robably because it's the
first time I've looked into a Mojo). Why can't we have a "dependentFeature"
tag?
2) Related to the first question: what is the purpose of "
prerequisiteFeatures" and "dependencyFeatures" parameters?
Thanks for any kind reply!
--
*Ing. Massimo Bono*
Ok, now my doubt has been cleared out.
Thank you!
2017-10-24 12:09 GMT+02:00 Jean-Baptiste Onofré :
> Correct.
>
> Regards
> JB
>
> On 10/24/2017 11:19 AM, Massimo Bono wrote:
>
>> In that case the user wouldn't interact with the browser, but with a
&g
from an OSGi service.
>
> Regards
> JB
>
> On 10/24/2017 09:24 AM, Massimo Bono wrote:
>
>> So, it's like saying:
>>
>> We know DOSGI implements RPC with REST-ful services, so we exploit that
>> in order to create some rest webservices. Then, instead of qu
vice
> that has to be exposed for remote call should contain
> exported.service.interface property).
>
> Regards
> JB
>
> On 10/23/2017 10:13 PM, Massimo Bono wrote:
>
>> Hello,
>>
>> I'm trying to grasp my mind on DOSGi; I want to have a general
ure I'm missing something, probably for my inexperience.
Can someone solves this question of mine?
Thanks!
--
*Ing. Massimo Bono*
28 matches
Mail list logo