You should use maven scope=provided for the org.osgi.service.*.annotations artifacts. They are not meant for runtime use and should not be part of a resolution operation. Don't install them in an OSGi framework.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow a
te the expected behavior as defined in the current Declarative Services
specification.
Tom
From: equinox-dev on behalf of Kanika Khattar
Sent: Wednesday, February 23, 2022 10:26 PM
To: equinox-dev@eclipse.org
Subject: [EXTERNAL] [equinox-dev] Issue with OSGI
As I don't have much to go by, I can just state some generic reasons for
this:
* The Component that feeds the Configuration to the ConfigAdmin is not
activated.
* The Configuration PID does not match the one given in the Component
annotation. If no special name is given, the full qualified Cla
Hi Jurgen,
Thank you for your quick response.
For the second question, Configuration is provided via ConfigurationAdmin.
Regards,
Kanika
On Thu, Feb 24, 2022 at 2:29 PM Jürgen Albert
wrote:
> Hi Kanika,
>
> all annotations that are provided by the OSGi Workinggroup (in the name
> space of org
Hi Kanika,
all annotations that are provided by the OSGi Workinggroup (in the name
space of org.osgi.*.annotations) expect the ones for the CDI Speci, are
compile time annotations. They must be part of our Targetplatform/ Build
Dependencies and might be used by your build tooling. This means
Hi All,
While using OSGI Annotations in my project, I am getting a few issues. It
will be great if you can help me with the same.
Below are the issues:
1.
*!ENTRY org.osgi.service.metatype.annotations 4 0 2022-02-24
09:43:01.813!MESSAGE FrameworkEvent ERROR!STA
