Bug 119419 - [model][classpath] Support for exclusion/inclusion filters in libraries
Summary: [model][classpath] Support for exclusion/inclusion filters in libraries
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: api
: 61386 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-12-06 10:35 EST by Jerome Lanneluc CLA
Modified: 2008-05-07 18:29 EDT (History)
8 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 Jerome Lanneluc CLA 2005-12-06 10:35:32 EST 
I20051130

Bug 113944 shows the need to support exclusion/inclusion filters on library entries. This would allow to hide/show packages/class files in a library without editing it (which cannot be easiliy done for jar files).
Comment 1 Jeff McAffer CLA 2005-12-08 09:53:07 EST 
See bug 98127 comment c38 for a detailed scenario.  It is unclear if this has anything to do with libraries since the code in question was all in my workspace.

Note also that completely hiding a package will give us the correct classpath behaviour (great!) but it would be very good to have a strategy for reporting the hiding in a case where ultimately the class is not found.

This issue is very important to PDE and it would be great if a solution could be found and implemented in the near future.
Comment 2 Philipe Mulet CLA 2005-12-09 05:23:16 EST 
Excluding a file is resulting in compiler not being able to load it, and if in binary form and referred to from binaries, it will abrupt from compilation entirely. This is why we added notion of access rules for allowing these types to be seen by compiler normally, but be flagged if referenced from sources.

If PDE was willing to compute exclusion rules in case it knows a more accessible version of a given type is present further down on the buildpath, then this could be used. But I believe you'd rather want a specific access rule for saying: FORBIDDEN_BUT_KEEP_LOOKING_FOR_BETTER_MATCH...
Comment 3 Philipe Mulet CLA 2005-12-12 05:10:11 EST 
This isn't currently on the 3.2 plan.
Comment 4 Philipe Mulet CLA 2006-09-13 07:33:35 EDT 
Suggestion in comment 2 got implemented for 3.2.
Still we should consider the support for exclusion/inclusion filters for library entries for improved flexibility in classpath configuration.

This combined with better compiler resilience to missing binaries (bug 156736) will improve the situation.
Comment 5 Jerome Lanneluc CLA 2007-01-11 06:41:27 EST 
(In reply to comment #4)
> Still we should consider the support for exclusion/inclusion filters for
> library entries for improved flexibility in classpath configuration.
This would indeed be nice to have. However this is time permitting (not a high priority for 3.3).
Comment 6 Frederic Fusier CLA 2007-03-14 10:51:26 EDT 
Unfortunately, not enough time to implement this in 3.3 time frame => defer
Comment 7 Frederic Fusier CLA 2007-06-19 09:12:59 EDT 
Reopen to reassign
Comment 8 Martin Aeschlimann CLA 2007-06-22 04:58:15 EDT 
*** Bug 61386 has been marked as a duplicate of this bug. ***
Comment 9 Philipe Mulet CLA 2007-08-31 12:26:27 EDT 
time permitting for 3.4
Comment 10 Jerome Lanneluc CLA 2008-05-07 18:29:32 EDT 
Deferring post 3.4