We do not have bnd-maven-plugin in our pom.xml.

Here's the MANIFEST.MF from the bundle. Not sure what you mean by logs. Manifest-Version: 1.0Bnd-LastModified: 1555356723270Build-Jdk: 1.8.0_201Built-By: preston.workBundle-ClassPath: .,signpost-core-1.2.jar,signpost-commonshttp4-1.2.jar, core.wcm.components.core-1.1.0.jarBundle-Description: Maven M...

I did go through the steps to resolve it in that document. Neither of the custom bundles we deploy exports core libraries. This is what bundle-plugin configuration looks like.<plugin>  <groupId>org.apache.felix</groupId>  <artifactId>maven-bundle-plugin</artifactId>  <extensions>true</extensions>  <...

We're having trouble where our project, during deployment, causes a restart of all the core AEM bundles on every deploy. We're not certain when this bug was introduced or how to solve it. There appears to be some documentation of an error like this, but I don't feel we meet this criteria - Custom bu...

I played around with the POM settings and figured out the problem. I was using version 1.26.0 of the Felix maven-scr-plugin dependency. Once I switched back to 1.20.0 this stared working correctly. So that plugin should look like this. <plugin><groupId>org.apache.felix</groupId><artifactId>maven-scr...

Try this use case meaning try a pom file like the above, but with a clean install and a basic component configuration?         

Why would labels and descriptions start working with AEM 6.3, though? Is there something we can do until we upgrade?    

We performed a 6.3 upgrade recently. For various reasons we stuck with Felix 1.9.8 annotations for now so I'm wondering if that's related. Anyway, labels and descriptions for our custom component configurations are missing. They look like this in the system config console. The code for our main pom....

Right. It's unfortunate in terms of documentation, though. I need to figure out how to call out documentation mistakes, because I think it is a mistake to have something marked as deprecated and not call out when the underlying functionality was removed. In terms of the solution, I've been working t...

I think this is what's throwing me off. When I think of deprecated I think of things that will be removed in the future. Not things that are being removed immediately. This feels like a documentation error on Adobe's part if I'm being honest. When I did the upgrade from 6.1 to 6.3 I explicitly looke...