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.
A project should somehow publish its metadata (from its physical extent) so that other projects linking against this one can find out what the extent is and incorporate it into its Logical model rather than generating new metadata for the included classes. We need to create a handshake mechanism between projects to solve this issue.
See document: http://java.netbeans.org/models/java/project-model.html
Svata's comment: Consider use-case: You have project and its sources parsed in MDR. After you build project, you get an output, e.g. Jar file. If you put Jar file to another project as a resource, you cannot use MDR metadata, because new Jar file has another codebase URI. (Proposal uses codebase URI as the unique identifier for classpath component. Metadata will be parsed again, because it's a new classpath component.)
This redundancy is acceptable in my opinion in this case: Consider situation when project output is used in another project as a resource. You can modify sources, compile classes. MDR metadata will be changed. But you need both - old output jar metadata and also new sources/classes metadata. They aren't the same. Another use-case is probably with subprojects (I'm not familiar, maybe next comment is completely wrong): Consider you have subproject. After you start building parent project, you will probably build subproject, if its output isn't up-to-date. In such case I can imagine that metadata could be shared.
The task is obsolete and it does not describe current module design. Closing as INVALID.