You could have several java files in your java agent. So why build the whole "project" every time you save one of the files. But that feature has caused me to scratch my head also a few times. At least it works differently than before... :)
The bigger annoyance for me is that by default (and I don't know how to get them back) the exception line numbers are lost from stack trace when the code is saved with 8.5.1.
One workaround is to save the code with 8.0 (or even 8.5 seems to work) client.
Below is the example of the same exception saved with 8.5.1 and 8.0.2:
8.5.1
java.lang.NullPointerException
at xx.xxx.xxx.utils.Search.getResultFieldValue(Unknown Source)
at xx.xxx.xxx.utils.Search.createResultDoc(Unknown Source)
at xx.xxx.xxx.utils.Search.NotesMain(Unknown Source)
at lotus.domino.AgentBase.runNotes(Unknown Source)
at lotus.domino.NotesThread.run(Unknown Source)
8.0.2
java.lang.NullPointerException
at xx.xxx.xxx.utils.Search.getResultFieldValue(Search.java:163)
at xx.xxx.xxx.utils.Search.createResultDoc(Search.java:115)
at xx.xxx.xxx.utils.Search.NotesMain(Search.java:59)
at lotus.domino.AgentBase.runNotes(Unknown Source)
at lotus.domino.NotesThread.run(Unknown Source)
So this seems to be a "feature" that has come with 8.5.1. Apparently the 8.5.1 client gives the java compiler an optimize parameter (-O or something) which causes the compiler to optimize the code and remove the stack trace line numbers. There is possibility to configure compiler options but I have not managed to figure out how to change the behavior back as it was before (or those compiler option configurations do not work). For me that is a big annoyance and makes debugging harder.
Btw: Has anyone figured out how to share the 8.5.1 LotusScript code templates among team or different client installations. I imagine it could be possible that one developer does the code templates and then some config file(s) are copied from 8.5.1 installation directory to other developers. But I haven't yet figured out where the 8.5.1 saves those template definitions.
You could have several java files in your java agent. So why build the whole "project" every time you save one of the files. But that feature has caused me to scratch my head also a few times. At least it works differently than before... :)
The bigger annoyance for me is that by default (and I don't know how to get them back) the exception line numbers are lost from stack trace when the code is saved with 8.5.1.
One workaround is to save the code with 8.0 (or even 8.5 seems to work) client.
Below is the example of the same exception saved with 8.5.1 and 8.0.2:
8.5.1
java.lang.NullPointerException
at xx.xxx.xxx.utils.Search.getResultFieldValue(Unknown Source)
at xx.xxx.xxx.utils.Search.createResultDoc(Unknown Source)
at xx.xxx.xxx.utils.Search.NotesMain(Unknown Source)
at lotus.domino.AgentBase.runNotes(Unknown Source)
at lotus.domino.NotesThread.run(Unknown Source)
8.0.2
java.lang.NullPointerException
at xx.xxx.xxx.utils.Search.getResultFieldValue(Search.java:163)
at xx.xxx.xxx.utils.Search.createResultDoc(Search.java:115)
at xx.xxx.xxx.utils.Search.NotesMain(Search.java:59)
at lotus.domino.AgentBase.runNotes(Unknown Source)
at lotus.domino.NotesThread.run(Unknown Source)
So this seems to be a "feature" that has come with 8.5.1. Apparently the 8.5.1 client gives the java compiler an optimize parameter (-O or something) which causes the compiler to optimize the code and remove the stack trace line numbers. There is possibility to configure compiler options but I have not managed to figure out how to change the behavior back as it was before (or those compiler option configurations do not work). For me that is a big annoyance and makes debugging harder.
Btw: Has anyone figured out how to share the 8.5.1 LotusScript code templates among team or different client installations. I imagine it could be possible that one developer does the code templates and then some config file(s) are copied from 8.5.1 installation directory to other developers. But I haven't yet figured out where the 8.5.1 saves those template definitions.