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

Bug 341904

Summary:

"Out of date target folder" warning message is displayed multiple times for the same project

Product:

[Technology] Tigerstripe

Reporter:

Navid Mehregani <nmehrega>

Component:

Core

Assignee:

Daniel Johnson <danijoh2>

Status:

CLOSED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

chrhartl

Version:

unspecified

Target Milestone:

0.5M0

Hardware:

OS:

Mac OS X - Carbon (unsup.)

Whiteboard:

Attachments:

Description	Flags
Problems View	none

Description Navid Mehregani

2011-04-05 09:46:33 EDT

Build Identifier: 

This defect is related to an enhancement submitted in the last iteration where target folder is marked "out of date" when workspace resources are modified.  It seems like this message gets outputted multiple times for the same project, which is a bit annoying. 
Please see attached snapshot.

Reproducible: Always

Comment 1 Navid Mehregani

2011-04-05 09:47:19 EDT

Created attachment 192556 [details]
Problems View

Comment 2 Navid Mehregani

2011-04-05 09:47:50 EDT

Assigning to Dan, since he submitted the original enhancement.

Comment 3 Chris Hartley

2011-04-07 00:17:01 EDT

I also think this would make more sense as an informational than a warning.

I don't see the point in clogging up the warning list with these.

Comment 4 Navid Mehregani

2011-04-07 11:00:39 EDT

(In reply to comment #3)
> I also think this would make more sense as an informational than a warning.
> 
> I don't see the point in clogging up the warning list with these.

As far as I know, I don't think you can log informational messages in the Problem view of Eclipse.  Keep in mind this is different than the Error Log view.

Comment 5 Chris Hartley

2011-04-08 00:18:05 EDT

TS already logs informational messages in the problem view.

Comment 6 Daniel Johnson

2011-04-12 18:16:13 EDT

I have committed the change to trunk. Not sure why you were seeing duplicate entries Chris, I was not able to reproduce that, but I did make the code more robust so it certainly should not happen anymore.