Bug 75329 - [classpath] Restrict visibility of Java Project content
Summary: [classpath] Restrict visibility of Java Project content
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.1 M3   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-29 14:10 EDT by Ede CLA
Modified: 2004-11-04 10:45 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ede CLA 2004-09-29 14:10:00 EDT 
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
Comment 1 Frederic Fusier CLA 2004-10-27 13:35:13 EDT 
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
Comment 2 Frederic Fusier CLA 2004-10-28 09:34:50 EDT 
Consider this requirement fixed by Access restriction.
I'll add it to JDT/Core build notes.
Comment 3 Frederic Fusier CLA 2004-11-04 10:45:07 EST 
Verified for 3.1 M3 with build I200411040800