Exactly, I forgot to mention that I did check documentation but I didn't found a method there, still, there should be a such API functionality that builds packages.

Hello,I am able to assemble a package using the JcrPackageManager assemble method, however in the package manager I get the package definition and the filters, but the package itself needs to be built. I am sure there should be a way, since it is possible via the HTTP interface using curl.Thanks.

See my late answer. Marked Robert answer as correct since that was in the right direction too.

Thanks Robert.And hi all. Yes, the issue was in part related to the uber-jar, you have to update to the uber-jar that matches your installation. 6.1, 6.1 SP1 or 6.1 SP2. But also, in my case, there was the aem-api dependency, I had to remove it since it was redundant. Of course, use depfinder to upd...

I was running AEM 6.1 with oak-auth-external 1.2.14, but after a hotfix (cq-6.1.0-hotfix-10832-1.0.zip) was installed with version 1.2.16 my bundle is unable to start.This dependency appears as unsolved:org.apache.jackrabbit.oak.spi.security.authentication.external,version=[1.0,2) -- Cannot be resol...

Thanks all, yes, I saw that this is different than the clustering I was referring to in 5.6. But after reading a little the trick to avoid this automatically offloading setup is editing /system/console/configMgr/org.apache.sling.discovery.impl.Config and leave Topology Connector URLs empty, this way...

Hello, I was installing a separate instance at 4504, but automatically AEM now creates a cluster and even offloading agents. Is there a way to prevent this default behaviour completely?Back in 5.6 there was a file repository.xml that you could edit, but I now cannot find a way to disable this in /sy...

leeasling wrote... Correct, it's a private hotfix that needs to be requested.  Thanks, private hotfix solves the issue.

Thanks, I filed a support ticket since I didn't find that hot package anywhere, neither here https://helpx.adobe.com/experience-manager/kb/aem61-available-hotfixes.html nor in the package share.

Firefox gets success=true