Bugzilla – Full Text Bug Listing
| Summary: | [classpath] Restrict visibility of Java Project content | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Ede <ede1> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | 3.0 | ||
| Target Milestone: | 3.1 M3 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
I think Access restriction covers your need... See JDTCore buildnotes contents about this new functionality: http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.eclipse.jdt.core/buildnotes_jdt-core.html?content-type=text/html Consider this requirement fixed by Access restriction. I'll add it to JDT/Core build notes. Verified for 3.1 M3 with build I200411040800 |
Hi all, I'm missing the possibility for a Java project to restrict the visibility of it's content. (Something pattern based like Properties->Java Build Path->Source Tab- >include/exclude) This would allow a Java Project to publish only it's "public" content to using projects. A use case example is the PDE. Currently a plugin project p1 using a plugin project p2 has complete access to the content of p2 even if p2 restricts it's export in it's plugin.xml. The plugin project p1 using some not exported classes of p2 will compile without errors, but cause a NoClassDefFoudError at runtime. Best regards Ede