I have just realized there is an 8.5 forum, so I am copying this into it… but i don’t see a way to remove this post, so please forgive the cross-posting.
. . .
The version is actually Domino Designer 8.5 but there is no option for that.
I am having a very strange problem with Java libraries which are imported from the file system (where I edit them with a standalone version of Eclipse, not the Domino designer Eclipse client).
Libraries simply disappear from any agent where they are imported, and the agent will not compile if it references classes from the library.
Steps to reproduce:
-
Create new Java library
-
Go into the Edit project button, and select file system
3a) Set the base directory to the …whatever/src directory of the Eclipse project where the source code lives OR to …whatever/src/toppackage (this may not be relevant, but I am including it just in case). The behavior is the same no matter how the base directory is set.
-
Import 1 or more classes or packages into the library.
-
Optionally, compile all the library (it will be successful if the work done in Eclipse was correct, which for me it is)
-
Save the library
-
Create a new Java agent or edit an existing Java agent
-
Go into the edit project dialog
-
Add the new Java Library to the agent with refresh button
-
Close the edit project dialog
-
Open the edit project dialog
-
The library no longer shows as included in the project on the right; also, references to the library cause errors because the classes are missing.
The files I am trying to import are all in packages with a hierarchy if that is relevant.
I am completely baffled, and hugely frustrated because this is blocking critical development paths, and working soley within the Designer’s java capabilities (since it doesn’t really take advantage of eclipse) is very difficult.
I have a scaffold that runs the code from within Eclipse using the JVM from within the Notes install, and the code itself works fine. So it is definitely something with designer.
. . .
BTW, in trying to get this to work, I have also discovered a full-on bug in the impport feature.
Although the following format is a legal character literal in Java (from very early on):
‘\u0034’
for any four hex digits, the importer fails and stops importing right after '\u0.
Fortunately, this is rather easy to work around in the code I support, but it is nonetheless an issue if anyone else has similar problems.
Thanks very much for any insight.