| Summary: | Rename org.eclipse.rap.help to org.eclipse.rap.doc? | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Ralf Sternberg <rsternberg> |
| Component: | Tools | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P1 | CC: | mknauer |
| Version: | 2.0 | ||
| Target Milestone: | 2.0 M4 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Ralf Sternberg
As far as I remember the old naming convention is split into * foo.bar.doc.user and * foo.bar.doc.isv If I am not mistaken and if I apply this convention to the RAP bundles, I end up with * org.eclipse.rap.doc.isv (for help about RAP Runtime and its API) If there was any RAP Tools specific documentation, it would go into 'org.eclipse.rap.tools.doc.user'. In order to avoid any potential future conflicts and confusion, I think we should take the opportunity to rename it now with 2.0. (In reply to comment #1) I'd rather keep it simple. There isn't too much documentation at the moment and I doubt that it will explode in the future. Splitting it up into runtime/tools and/or into user/isv would make it more complicated to find the right information. Instead of the one and only "RAP Developer's Guide" we'd end up with more guides such as a "RAP Tools Guide" etc. Moreover, it's probably hard to separate runtime and tools documentation because the are closely related. > In order to avoid any potential future conflicts and confusion, I think we > should take the opportunity to rename it now with 2.0. I agree. Although this will change the pattern of our help URLs, I think we should do that now. I am going to rename it to 'org.eclipse.rap.doc' then. Implemented in commit f8e81799705fb3712971e20db9bd388e5cfb343d. |