Description Paul Clenahan 2005-12-14 14:12:25 EST

In my Eclipse environment, I had "Build Automatically" set for my BIRT project (default setting?). This obviusly attempts to build the project. The user could also do the same action from the Eclipse "Project" menu if they select "Build All", for example.

(It should also be noted that many Eclipse users may think they have to build a BIRT report since they are used to idea of "building" things.)

In BIRT 1.0.1, building a project that only contained reports would not generate any errors. So the "build" action did not have any impact.

In BIRT 2.0 M3, building a project that contains only reports actually generates an error message:

"The project was not built due to "<project name> does not exist". Fix the problem, then try refreshing this project and building it since it may be inconsistent."

This is a problem since it makes the user think there is something seriously wrong when in fact there is not. There is also nothing the user can do to correct the error message.

We need to return to the BIRT 1.0.x behavior where no message is generated if there is not code in the project that can be built.