I am also facing the same error and yes - the server was stopped before creating install folder and re-starting the instance.I also have the same maven & java versions

Hello,Thank you for your response. I was wondering if you had some availability today for a web session?

Hello,Thanks for your comment. I had also tried this but it uses the same import which is providing the "import cannot be resolved" errors. The example code similarly uses the com.mergeandfuse.getserviceuserresolver.GetResolverThis uses the GetResolver which comes from the zip file attachment from S...

Hello, Thanks for your comment. Yes, I tried to reference the jar from another area but unfortunately its still not resolving. I also ensured to update pom.xml file to accomodate the change.

... continuing the rest of pom.xml from root directory as it was too large for previous message: <!-- ====================================================================== --> <!-- D E P E N D E N C I E S --> <!-- ====================================================================== --> ...

Hello Girish,Here are the pom files.core>pom.xml <?xml version="1.0" encoding="UTF-8"?> <!-- | Copyright 2017 Adobe Systems Incorporated | | Licensed under the Apache License, Version 2.0 (the "License"); | you may not use this file except in compliance with the License. | You may obtain a ...

Hello Girish, thank you for providing the info, I have ensured to add the jar inside the project. It is the same way you have added in your Java Build Path within the Libraries section: 

Yes, thats correct. Even after uploading, starting and adding the bundle, the import is still not resolving.

Yes, I have followed the steps. I have ensured to follow Steps 1-9 and 1-5 from the link here. I uploaded and started the DevelopingWithServiceUser.jar bundle and ensured it was active. I have also added certificate to global trust store, corresponding private key and user mapping settings for fd-se...

Thanks for your comment - unfortunately it still does not pick it up. I had a colleague try as well and they experienced the same problem. Unsure if this jar is correct.The general idea is to use ResourceResolver to obtain the service user somehow. In this case, by  resourceResolver = getResolver.ge...