Velocity
  1. Velocity
  2. VELOCITY-38

Problems with recursive macro calling when using #set with "" (doublequotes)

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 1.2
    • Fix Version/s: None
    • Component/s: Engine
    • Labels:
      None
    • Environment:
      Operating System: Linux
      Platform: PC

      Description

      Because of use of #set statements of this kind:
      #set($test = "blah blah $value")
      macros are not being called.
      It looks like they were not defined.
      Output looks like this:
      #testMacro

        Activity

        Hide
        Damian Gajda added a comment -

        Created an attachment (id=1206)
        This is an example of a template which shows the way this bug works.

        Show
        Damian Gajda added a comment - Created an attachment (id=1206) This is an example of a template which shows the way this bug works.
        Hide
        Geir Magnusson Jr added a comment -

        thx. acked.

        Show
        Geir Magnusson Jr added a comment - thx. acked.
        Hide
        Will Glass-Husain added a comment -

        Created an attachment (id=8762)
        results when running test case on 1.4rc1

        Show
        Will Glass-Husain added a comment - Created an attachment (id=8762) results when running test case on 1.4rc1
        Hide
        Will Glass-Husain added a comment -

        Well, this is an old bug with a confusing test case. I tried the test case in
        the latest version of Velocity (1.4rc1), and the macro is being called 6
        times. As I read the original report, this didn't happen for Damien with
        version 1.2.

        As I think this is the desired behavior (no expected test case is given), I'm
        going to mark this fixed. If there's still a problem, please reopen and
        provide a simple test case showing desired vs. expected output. (I've
        attached a text version of my test results). Thanks.

        Show
        Will Glass-Husain added a comment - Well, this is an old bug with a confusing test case. I tried the test case in the latest version of Velocity (1.4rc1), and the macro is being called 6 times. As I read the original report, this didn't happen for Damien with version 1.2. As I think this is the desired behavior (no expected test case is given), I'm going to mark this fixed. If there's still a problem, please reopen and provide a simple test case showing desired vs. expected output. (I've attached a text version of my test results). Thanks.
        Hide
        Henning Schmiedehausen added a comment -

        Close all resolved issues for older releases.

        Show
        Henning Schmiedehausen added a comment - Close all resolved issues for older releases.

          People

          • Assignee:
            Unassigned
            Reporter:
            Damian Gajda
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development