Automatic Dependency Configuration can not be cloned

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 2.7 beta2, 2.7
    • Affects Version/s: None
    • Component/s: None
    • None

      When cloning a plan with the automatic dependency management turned on, the configuration is not cloned correctly. Its still got the id of the job in the old chain, rather than the id of the job in the new chain.

      2010-10-11 12:25:53,556 ERROR [316196497@qtp-1176734279-13] [runtime] Expression dependencyProviderJob is undefined on line 6, column 22 in chain/view/viewAutomaticDependencyManagement.ftl.

      Expression dependencyProviderJob is undefined on line 6, column 22 in chain/view/viewAutomaticDependencyManagement.ftl.
      The problematic instruction:
      ----------
      ==> ${dependencyProviderJob.name} [on line 6, column 20 in chain/view/viewAutomaticDependencyManagement.ftl]
      in user-directive ww.param [on line 6, column 9 in chain/view/viewAutomaticDependencyManagement.ftl]
      in user-directive ww.text [on line 4, column 5 in chain/view/viewAutomaticDependencyManagement.ftl]
      ----------

      Java backtrace for programmers:
      ----------
      freemarker.core.InvalidReferenceException: Expression dependencyProviderJob is undefined on line 6, column 22 in chain/view/viewAutomaticDependencyManagement.ftl.
      at freemarker.core.TemplateObject.assertNonNull(TemplateObject.java:124)
      at freemarker.core.TemplateObject.invalidTypeException(TemplateObject.java:134)
      at freemarker.core.Dot._getAsTemplateModel(Dot.java:78)

            Assignee:
            Przemek Bruski
            Reporter:
            bmccoy
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: