Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-291

multiple execution of "_buildmagic:init"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • No Release
    • None
    • Build System
    • None

      SourceForge Submitter: mcbain4711 .
      <target name="init" unless="init.disable"
      depends="_buildmagic:init"/>

      Ant always executes the "depends" targets. The unless
      attribute only prevents the execution of the target "init"
      (where the unless ist used).

      The idea of property "init.disable" is to prevent the
      multiple initialization of the buildmagic-system.
      This property is set to "true" at the end
      of "_buildmagic:init" target.
      Without using "antcall" Task it is not nessessary to do
      so, because ant only run the init target once,
      independently the number of dependencies on "init" in
      other targets. Maybe ant calculates the graph of target
      execution order and call every target only once...

      This does not match to the case in which antcall is used.
      With antcall the "only-once" rule is broken and for every
      single antcall the buildsystem??????????????????s init targets are
      executed.
      This makes the "configure" target a lot of times and
      makes the whole build very slow. Beside the build-
      output is polluted by the "Overriding previous definition of
      reference to ..." messages.

      Solution: move the unless="init.disable" to the
      target "_buildmagic:init" (common.xml) !

              starksm64 Scott Stark (Inactive)
              sourceforge-user SourceForge legacy user (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: