-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Domino 14 -- domino_java_tools -- package lotus.domino does not exist #7
Comments
For this error, it looks like Notes.jar was not found. We need to locate it under the Domino installation, and add it to the classpath when compiling the JARs. The current code is here: Lines 17 to 29 in 15ae138
|
This command should work to locate the JAR:
From there, we could add a condition for this line to use the new path on Domino 14.0. However, note that build.gradle is not a J2 template currenlty. I was envisioning adding a condition to check this in build.gradle, similar to this for Notes Client 14.0: https://github.com/Moonshine-IDE/DominoAPILocalExample/blob/2c5023ba8d14f3e778b9a48183bcd65b29fc0fe7/build.gradle#L35-L40 |
I have updated this, and it appears to run, but as me and @JoelProminic found out during our testing of the Domino 14 and Nomad, it doesn't appear to actually update the user acls. Lines 23 to 30 in 12b0b0c
|
Right, we saw that the agent ran and made updates to:
However, when we checked names.nsf, we did not see these changes. We looked for an extra copy of names.nsf, but did not find anything obvious. The current plan is to revert to Domino 12.0.2 and confirm that the roles are still working properly there. |
Preparing for Domino 14, I am getting the following error in the current Ansible role: domino_java_roles
https://github.com/STARTcloud/hcl_roles/tree/main/roles/domino_java_tools
The text was updated successfully, but these errors were encountered: