• Anonymous
  • Login
  • Register



JAVADDIN - Defect: documentation improvements

Created on Nov 24, 2010
Created by Harald Albers
Status Submitted
Release 1.3.0

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}.




Taken Actions by Owners

No actions have been taken yet.


Documents
     
Creation Date
Author
Subject
Nov 24, 2010 Harald Albers documentation improvements
Nov 24, 2010 David D Taieb     Response: Thank you. Nice catches
     
In this field you can enter the actual defect.

You can use the rich text editor for rich text formating. You can also enter HTML to embed objects, e.g. to embed a YouTube video or a screenshot of the project. In this case use '[' and ']' to mark the passthrough HTML as such.

Please note that the first time you use the new UI your description is converted from rich text to MIME. You might want to copy and paste the raw plain text from the old UI in the new UI so that you don't loose information.
In this field owners can describe what they have done or want to do.

You can use the rich text editor for rich text formating. You can also enter HTML to embed objects, e.g. to embed a YouTube video or a screenshot of the project. In this case use '[' and ']' to mark the passthrough HTML as such.

Please note that the first time you use the new UI your description is converted from rich text to MIME. You might want to copy and paste the raw plain text from the old UI in the new UI so that you don't loose information.