Bug 40684 - tasks associated with wrong project when using injars
Summary: tasks associated with wrong project when using injars
Status: RESOLVED FIXED
Alias: None
Product: AJDT
Classification: Tools
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 2000
: P2 normal (vote)
Target Milestone: ---   Edit
Assignee: Sian Whiting CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-23 19:15 EDT by Ron Bodkin CLA
Modified: 2004-07-27 04:45 EDT (History)
0 users

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 Ron Bodkin CLA 2003-07-23 19:15:18 EDT 
If I use declare warning to add warnings to an external project, the Eclipse 
tasks (warnings) are tied in to the source project, not the AspectJ project 
that generated them. I.e.,
1) create a Java project, sourceproj
2) export the classes as source.jar
3) create an AspectJ project, warningsproj, that takes source.jar as an injar 
with some declare warning statements that match source
4) compile warningsproj
5) close warningsproj
the warnings remain in the task list, associated with source
Comment 1 Ron Bodkin CLA 2003-07-23 19:19:48 EDT 
The bug I'm seems to be more complicated than I first thought. When I 
recompiled my warningsproj to not include sourceproj, the sourceproj warnings 
remain; I can't seem to clear them in any way.
Comment 2 Wes Isberg CLA 2003-08-06 02:06:44 EDT 
ditto!  I really regret creating a system-wide test that created hundreds of
task items.  Any workarounds?
Comment 3 Mik Kersten CLA 2003-08-15 11:40:34 EDT 
This may already be resolved by the fix of cleaning up project tasks, but we 
should verify.
Comment 4 Sian Whiting CLA 2004-07-26 12:22:51 EDT 
Tested in 1.1.11 and the warnings are now associated with the correct project.
Comment 5 Sian Whiting CLA 2004-07-27 04:45:47 EDT 
Fixed in 1.1.11