• documentation improvements

    By Harald Albers 4 years ago

    Evaluating javaddin 1.3 I found the following minor problems in the 1.3 version of the pdf document:

    Page 2 - Overall architecture:

    You should be able to simply copy these 10 plugins in the {notesbin}/javaddin/rcp/eclipse
    directory

    should be

    You should be able to simply copy these 10 plugins in the {notesbin}/javaddin/rcp/eclipse/plugins
    directory

     

    Page 3 - enumeration 6.

    org.openntf.javaddin.sample_1.0.0.XXXX.jar: jar file that must be installed in
    {dominobin}/shared/eclipse/plugins directory

    should be

    org.openntf.javaddin.sample_1.0.0.XXXX.jar: jar file that must be installed in
    {dominobin}/javaddin/shared/eclipse/plugins directory

     

    page 12 - last paragraph:

    Add Note.jar the JRE seetings

    should be

    Add Notes.jar to the JRE seetings

     

    page 13

    To fix this problem, you can do the following: use
    Windows\preferences\Java\Compiler\Errors-Warnings and select Ignore in the
    Forbidden references (access rules) field

    the setting is easier to locate if described as follows

    To fix this problem, you can do the following: use
    Windows\preferences\Java\Compiler\Errors-Warnings\Deprecated and resticted API and select Ignore in the
    Forbidden references (access rules) field

     

    page 15 - 3.

    The documentation mentions two different directories as the deployment target. This should be clarified.

    {notesdata}domino\workspace-javaddin\applications\eclipse\plugins
    “c:/domino/javaddin/shared/eclipse”

     

    Througout the document, two different varables are used for the same thing: {notesbin} and {dominobin}.

    • Thank you. Nice catches

      By David D Taieb 4 years ago

      They are all very valid. I will fix these documentation issues in the next release