This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Layer file documentation | ||
---|---|---|---|
Product: | platform | Reporter: | puce <puce> |
Component: | Documentation | Assignee: | Jesse Glick <jglick> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | tomwheeler |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
puce
2008-10-25 14:04:31 UTC
Seems you missed http://wiki.netbeans.org/DeclarativeRegistrationUsingAnnotations *** This issue has been marked as a duplicate of 149136 *** Isn't the point about the documentation (ignoring the request for enhancement about how layer files could be improved) still valid? I don't know of any comprehensive documentation on the contents of the System Filesystem. All I was able to find was the DTD and a incomplete set of module-by-module examples in the Javadoc. I asked on the dev@openide list and no one else could point me to anything more. So while I agree that the annotation-based approach described in #149136 negates to some extent RFEs for layer files, it does not address documenting what could possibly go into a layer file. Based on your preference, I will either reopen this issue or open a new one regarding system filesystem documentation. If annotations are available for SPIs you might like to use (and clearly displayed in the regular Javadoc for that module), then there is no need for an existential list of possible SFS entries. What would you use it for? Regarding the existing index of SFS entries in Javadoc - if you find particular items that are missing, please file a defect for the corresponding module, as every module's arch.xml is supposed to enumerate these things. A general issue complaining that the list is incomplete will have no particular owner and will likely be ignored. |