http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1587 *** shadow/1587 Tue May 1 08:48:24 2001 --- shadow/1587.tmp.27643 Tue May 1 09:22:45 2001 *************** *** 2,11 **** | Macros from separate templates conflict | +----------------------------------------------------------------------------+ | Bug #: 1587 Product: Velocity | ! | Status: NEW Version: 1.0-Release | ! | Resolution: Platform: PC | | Severity: Normal OS/Version: Windows NT/2K | ! | Priority: Component: Build | +----------------------------------------------------------------------------+ | Assigned To: [EMAIL PROTECTED] | | Reported By: [EMAIL PROTECTED] | --- 2,11 ---- | Macros from separate templates conflict | +----------------------------------------------------------------------------+ | Bug #: 1587 Product: Velocity | ! | Status: RESOLVED Version: 1.0-Release | ! | Resolution: INVALID Platform: PC | | Severity: Normal OS/Version: Windows NT/2K | ! | Priority: High Component: Build | +----------------------------------------------------------------------------+ | Assigned To: [EMAIL PROTECTED] | | Reported By: [EMAIL PROTECTED] | *************** *** 35,38 **** them was showing the wrong information. Changing the macro name fixed the problem as a workaround, but managing this when we're planning to have hundreds of templates is not an option. Each template should have its own macro ! namespace to prevent conflicts like this. --- 35,45 ---- them was showing the wrong information. Changing the macro name fixed the problem as a workaround, but managing this when we're planning to have hundreds of templates is not an option. Each template should have its own macro ! namespace to prevent conflicts like this. ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-05-01 09:22 ------- ! Please try reading the documentation before posting a bug report. This ! functionality is clearly documented under the VelociMacro portion of the ! developer guide: ! ! http://jakarta.apache.org/velocity/developer-guide.html#config
