Bug 427559 - export restrictions on source folder
Summary: export restrictions on source folder
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.3.1   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-06 08:06 EST by Missing name CLA
Modified: 2014-09-10 23:42 EDT (History)
1 user (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 Missing name CLA 2014-02-06 08:06:55 EST 
It is not possible to exclude either source folders of packages from being exported to other projects.

This was reported before in bug 29865 (and some others). Those where solved by allowing import restrictions on both libraries and projects. While this is a useful feature, and can have the same result, it's not quite the same as an export restriction. 

It would be very convenient to be able to define these restrictions in a single location; at the same location as the actual code. The current solutions requires me to add the restriction to all the depending project. 

A workaround is to create a project B, make it depend on the actual project A, punt restrictions on this import, then export project A. Project C, D, and E can then depend on B instead of A. However, this doubles the amount of projects and feels really wrong.