http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1509
*** shadow/1509 Wed Apr 25 11:47:25 2001 --- shadow/1509.tmp.18537 Thu May 10 07:46:13 2001 *************** *** 2,8 **** | Project object not fully functional in BuildEvents | +----------------------------------------------------------------------------+ | Bug #: 1509 Product: Ant | ! | Status: NEW Version: 1.3 | | Resolution: Platform: PC | | Severity: Normal OS/Version: Windows NT/2K | | Priority: Medium Component: Core | --- 2,8 ---- | Project object not fully functional in BuildEvents | +----------------------------------------------------------------------------+ | Bug #: 1509 Product: Ant | ! | Status: ASSIGNED Version: 1.3 | | Resolution: Platform: PC | | Severity: Normal OS/Version: Windows NT/2K | | Priority: Medium Component: Core | *************** *** 41,44 **** null null null ! null --- 41,61 ---- null null null ! null ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-05-10 07:46 ------- ! This is a chicken and egg problem to some extent. The problem is do ! buildListeners expect to receive a buildStarted before they receive any otehr ! events. If I move the build started event generation, then you will receive a ! number of message events prior to the buildStartedEvent. ! ! There are three possible courses of action that I see. ! 1. Add in an additional event - ProjectConfigured or something like that ! 2. Move the firing of the buildStarted event to just before the execution of ! the first target and indicate that events can be received prior to the ! buildStarted event ! 3. Don't change anything but make it clear that the Project object will not be ! fully initialised at this time. ! ! In the last case, the workaround is to defer access to the Project until you ! receive the first targetStarted event.
