Ok, I found the solution and it was simple indeed.
When using
org.apache.felix:org.apache.felix.scr.annotations:1.9.4
as Maven depenency and
org.apache.felix:maven-scr-plugin:1.7.2
as Maven plugin then no service component descriptor is generated but no warning either.
Then of course the decorator is not active.
When using org.apache.felix:maven-scr-plugin:1.20.0 it works as it should.
I guess sometimes one just has to sleep over a problem. ;-)

Best,

Sandro


Am 28.10.14 21:50, schrieb Sandro Boehme:
Hello,

I was wondering why I can't install the resource-editor bundle to the
Sling server. It took me a significant amount of time to figure out that
the changes will be installed if I use the 1.6.0 version of
org.apache.felix:org.apache.felix.scr.annotations instead of a newer one
[1].
I don't get any error message. To test if the installation was
successful I added a static variable to a ResourceDecorator and checked
if a log output was showing the changed value.

I don't use a different/incompatible major version of
oaf.scr.annotations and the change log [3] doesn't show any
incompatibilities.
I don't see any syntax problems and when debugging the Felix bundle
servlet and the Maven-Sling-Plugin I didn't find any hidden exceptions
that are thrown. The installation looks like it would be successful.

This might be just a simple problem. But it would make my day if someone
has a solution.

A dedicated project can be found at GitHub [4]

[1] -
https://github.com/sandroboehme/sandbox/blob/master/scr-annotation-test/pom.xml


[2] -
https://github.com/sandroboehme/sandbox/blob/master/scr-annotation-test/src/main/java/de/sandroboehme/scrannotationdeployment/ADecorator.java


[3] -
http://svn.apache.org/repos/asf/felix/releases/org.apache.felix.scr.annotations-1.9.8/changelog.txt


[4] -
https://github.com/sandroboehme/sandbox/tree/master/scr-annotation-test

Thanks a lot,

Sandro


Reply via email to