Bug 546794 - [9] Evaluate module-related classpath attributes on source folders
Summary: [9] Evaluate module-related classpath attributes on source folders
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.12   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug bulk move
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-28 06:04 EDT by Stephan Herrmann CLA
Modified: 2022-09-17 20:32 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 Stephan Herrmann CLA 2019-04-28 06:04:01 EDT 
With the new UI from bug 546352 users will be able to define module related attributes also on source folders. We need to ensure that those are properly evaluated.
Comment 1 Stephan Herrmann CLA 2019-05-20 18:00:12 EDT 
Request for comments:

With the new UI, users are invited to use these attributes in more locations.
With JDT/Core not evaluating these on source folders, users will be disappointed.

I can offer to do one of two things for RC1:

- implement one or two scenarios of using module related attributes on source folder, preferably the most likely use cases :)  maybe there *is* only one ...

- implement a warning in the UI, when attributes are set on source folders (i.e., affecting the current project)

WDYT?
Comment 2 Manoj N Palat CLA 2019-08-27 02:06:09 EDT 
Bulk move out of 4.13
Comment 3 Eclipse Genie CLA 2022-09-17 20:32:07 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.