Aem asset create api is deprecated on aem cloud and it’s because of the reason that assets now don’t resides  on aem repository instead the binary go to s3 bucket so your existing servlet won’t work for aem cloud. it seems for your use case you can either use asset upload api as explained on https:/...

Above explained strategy was used before when aem maven project archetype doesn’t supported the react or angular project. No harm in that. Many projects are still running in that old fashioned way

Try updating the maven plugin locally and also on your IDE.   https://stackoverflow.com/questions/47920305/can-not-set-org-eclipse-aether-spi-log-logger-with-custom-maven-plugin

I believe you want same sling model to return different json output based on the selector in the url. If that’s the case then on your sling model you can read the selector and based on that value to  in can return the json of corresponding component. final String selectorString = request.getRequestP...

Sling model can be registered with resourceType of your aem component. I don’t think you need to register anything here. In your sling model you can read the sling selector from the url and send the response accordingly based on selector value. But in this case you need to adapt your sling model usi...

If you inspect the link on browser do you see .html append in the href ? Is the behaviour same on author, publisher and dispatcher?

I know that metadata is read only on Brand Portal. I need the opinion from the community advisor if they have suctioned any thing similar in the past.   As in our use case Agency will be uploading the assets on BP and not in AEM so what are the ways we can get the metadata information from them back...

Hi, I do have a requirement where users in brand portal can upload the asset in brand portal contribution folder but i don't see the option to update the metadata field on brand Portal. in our requirement i don't want to give brand portal user access to AEM assets(licensing constraint) so what shoul...

Then I believe your config.publish OSGI config is not working. Can you check on developer console if you see your OSGI config for publisher and is it the custom service on which you are calling the externalizer for publish?

Is it taking http://localhost:4504 ?