| Summary: | GEF & Draw2D doc plugins do not contain javadoc reference | ||
|---|---|---|---|
| Product: | [Tools] GEF | Reporter: | Brian Lillie <brianlil> |
| Component: | GEF-Legacy GEF (MVC) | Assignee: | Anthony Hunter <ahunter.eclipse> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ahunter.eclipse, hudsonr, raji |
| Version: | 3.4 | ||
| Target Milestone: | 3.4.0 (Ganymede) RC4 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Brian Lillie
So you are saying you take the GEF-SDK download and remove the source? This sounds like a reasonable request, but I'm just wondering what is the reason for depriving developers of the source code should they need to debug or just verify the javadoc's claims? Is source being left out of this "platform" for legal/contamination reasons? ... or, can you not answer that question for legal reasons ;-) Randy, you pretty much nailed it :) What's the difference between ... ... ah, never mind, I'll get in trouble for that. The product delivery is not including any of the eclipse source, but we are able to include the doc plugins. Since we are providing our own target platform, including the doc plugins into the target platform allows for the content assist/auto complete to show javadoc assistance. With source, the javadoc would normally come from the source, but by using the ext allows it to be found from the doc plugins. Documentation fix, so OK to commit to HEAD for 3.4 RC4. |