Do you mean to say that the console "Sling Resource Resolver (/system/console/jcrresolver)"  doesn't show you updated rules immediately or it appears in console but it doesn't work when you try to access it in browser (either via publish directly or dispatcher)?

Have you configured a separate datastore in 6.2?  If not then use segment-no-dsSource RepositoryTarget RepositoryProfileAdditional Flagscrx2 or TarMK with FileDataStoreTarMKsegment-fdsSee Troubleshooting section belowcrx2MongoMKmongo-from-crx2 -T mongo-uri=mongo://mongo-host:mongo-port -T mongo-db=m...

this is most likely an issue caused with wrong JVM version being used with AEM 6.0 (outdated)Use 1.7 rather than 1.8

What archetype version did you follow? I can see that you've manually edited the version numbers of specific libraries.Refer GitHub - adobe/aem-project-archetype: Maven template to create a new Adobe Experience Manager (AEM) project as starting … Pick a version based on your AEM/SP and it should wor...

Could you share the error.log and stderr.log snippets?

Do you have any 'xml files under OSGI-INF/lib folder?  Do you use Spring or other framework libraries in this code bundle? <Embed-Directory>OSGI-INF/lib</Embed-Directory><Embed-Transitive>true</Embed-Transitive>

To me, it seems that you're using extender pattern here and this bundle in itself registered as an extendee though I don't see any 'fragment' header in manifest. This doesn't seem usual thing to me unless its a fragement bundle or marked for another container.Require-Capability: osgi.extender;filter...

Are you using DS1.3 or a mix-match of DS & SCR annotations? Do you have bnd-maven-plugin in your pom.xml?snippet from manifest -Require-Capability: osgi.extender;filter:="(&(osgi.extender=osgi.component)(version>=1.3.0)(!version>=2.0.0)))"

Could you share the logs and MANIFEST.MF of your bundle as mentioned by Jörg?Are you dispatching any kind of events from your code or have bundle-activators performing any task(s)?Brightcove (com.coresecure.brightcove.cq5.brightcove-services) shouldn't be a problem, it doesn't export any core servic...

Include  "bom" and "aws-java-sdk-cloudfront"  in Embed-Dependencyexample:<plugin><groupId>org.apache.felix</groupId><artifactId>maven-bundle-plugin</artifactId><extensions>true</extensions><configuration><instructions><Bundle-SymbolicName>${project.artifactId}</Bundle-SymbolicName><Bundle-Name>${pro...