Bug 115495 - [classpath] allow finer granularity for api access rule specification
Summary: [classpath] allow finer granularity for api access rule specification
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 157549 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-11-08 10:45 EST by Ernest Pasour CLA
Modified: 2007-06-20 03:32 EDT (History)
4 users (show)

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 Ernest Pasour CLA 2005-11-08 10:45:49 EST 
The idea of being able to specify access rules for a jar is great.  Right now,
as far as I am aware, the only granularity is at the class level.  We would like
to additionally be able to specify methods and fields within a class whose
accesses are "Allowed", "Discouraged access" or "Forbidden".  It would be nice
to have enough flexibility to choose the default behavior for a rule as well
(i.e. this method is forbidden, this one is allowed, all others are discouraged).
Comment 1 Philipe Mulet CLA 2005-11-09 03:52:11 EST 
This is a valid point, and we had it in mind; but this is not a committed item
for 3.2.
Comment 2 Frederic Fusier CLA 2006-11-05 06:36:05 EST 
*** Bug 157549 has been marked as a duplicate of this bug. ***