Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 126703 - Resource */build.properties does not exist in .log
Summary: Resource */build.properties does not exist in .log
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2 M5   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-07 04:35 EST by Dani Megert CLA
Modified: 2006-02-10 04:09 EST (History)
1 user (show)

See Also:

Attachments
stripped project (2.81 KB, application/octet-stream)
2006-02-07 05:03 EST, Dani Megert CLA 		no flags Details
View All 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 Dani Megert CLA 2006-02-07 04:35:59 EST 
I20060131-1200

Each time a project is built that has no build.properties I get the following .log entry but no warning or error in the UI:

!ENTRY org.eclipse.core.resources 4 368 2006-02-07 10:29:28.839
!MESSAGE Resource /W-JAX Talk 2005/build.properties does not exist.

I would expect that an error or warning marker is attached to my project or plugin.xml and no exception being written to .log.

Note: I've set 'Problems in Build propoerties' to 'Error'.
Comment 1 Wassim Melhem CLA 2006-02-07 04:44:30 EST 
Is there something special about this project? 

I just created a hello world plugin, deleted its build.properties, and built several times (incrementally and full), and everything went fine.
Comment 2 Dani Megert CLA 2006-02-07 04:53:13 EST 
>Is there something special about this project? 
Not that I know. I will attach a stripped version of it.
Comment 3 Dani Megert CLA 2006-02-07 05:03:05 EST 
Created attachment 34261 [details]
stripped project
Comment 4 Wassim Melhem CLA 2006-02-10 04:09:57 EST 
Just happened to me.  There was a key place in which we were not checking for the existing of a build.properties file before reading it.  Fixed.