Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 324885

Summary: Libraries "added to application" marked with warning that they are not exported
Product: [WebTools] WTP Java EE Tools Reporter: Paul Fullbright <paul.fullbright>
Component: jst.j2eeAssignee: jst.j2ee <jst.j2ee-inbox>
Status: REOPENED --- QA Contact: Chuck Bridgham <cbridgha>
Severity: enhancement    
Priority: P3 CC: konstantin, neil.hauge
Version: 3.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows Vista   
Whiteboard:

Description Paul Fullbright CLA 2010-09-09 14:33:58 EDT 
When using a user library as a library provider, and including the library with the application, should the library not be marked as exported?

This is more a question than an adamant bug report, but it certainly *seems* to me that it should be marked that way.  Projects created without this setting automatically have a warning that the library is included but not exported.

This was found in head code.
Comment 1 Konstantin Komissarchik CLA 2010-09-09 14:43:30 EDT 
I'd file a bug for that warning message. It seems dubious to me. It is perfectly valid to not re-export your dependencies and that is the default behavior for JDT. It makes sense for us to follow that. At most, I can see adding a checkbox to let the user manually toggle export flag (default would be off). Seems fairly low value enhancement though as users can already export libraries via existing JDT means if they need to be exported. Feel free to open an enhancement request for that if you'd like to pursue that.
Comment 2 Paul Fullbright CLA 2010-09-09 14:51:53 EDT 
This is a j2ee validation marker, correct?
Comment 3 Konstantin Komissarchik CLA 2010-09-09 15:02:34 EDT 
Indeed.
Comment 4 Paul Fullbright CLA 2010-09-09 15:10:45 EDT 
Reopening, as the issue is still the same (warning shows up for new project), the component is the same, and I'd like to preserve the information.

Changing the title, the severity, and the request:  is this validation warning necessary for these situation?