Forrest
  1. Forrest
  2. FOR-145

Make Forrest able to be imported by Ant

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 0.7
    • Fix Version/s: None
    • Component/s: Compile
    • Labels:
      None

      Description

      I use an ant build system called antworks,
      http://antworks.sourceforge.net/
       which includes an antlet for forrest.
      Antlets are included into a projects build file with a ant <import> task.

      However forrest has many common target names and properties.
      Please prefix all targets and properties with "forrest." to support using ant import of the entire forrest.build.xml
      1. core.target.diff
        65 kB
      2. main.build.diff
        22 kB
        Thorsten Scherler

        Issue Links

          Activity

          Hide
          Nicola Ken Barozzi added a comment -
          I'd call this a bug, as it prevents importing, an d changed the description.

          The prior description was the cure, not the problem:

           * prefix ALL targets with "forrest." for easier importing
          Show
          Nicola Ken Barozzi added a comment - I'd call this a bug, as it prevents importing, an d changed the description. The prior description was the cure, not the problem:  * prefix ALL targets with "forrest." for easier importing
          Hide
          Dave Brondsema added a comment -
          We should fix this for 0.6.1 too, if possible.
          Show
          Dave Brondsema added a comment - We should fix this for 0.6.1 too, if possible.
          Hide
          David Crossley added a comment -
          The existing issue is FOR-145. We seem to keep delaying such important issues.
          Show
          David Crossley added a comment - The existing issue is FOR-145 . We seem to keep delaying such important issues.
          Hide
          Thorsten Scherler added a comment -
          I started to prefix all targets.

          An observation is that we now need to add the "forrest." prefix as well calling forrest.

          When we did in main/ ./build.sh clean we now have to use ./build.sh forrest.clean
          Show
          Thorsten Scherler added a comment - I started to prefix all targets. An observation is that we now need to add the "forrest." prefix as well calling forrest. When we did in main/ ./build.sh clean we now have to use ./build.sh forrest.clean
          Hide
          Thorsten Scherler added a comment -
          patch against build.xml
          Show
          Thorsten Scherler added a comment - patch against build.xml
          Hide
          Thorsten Scherler added a comment -
          The last attachment core.target.diff (65 kb) is a refactoring of all core targets.

          Since this patch will break a lot of build systems that are using the old targets we need to reach a decision how to we apply the patches to close this issue.
          Show
          Thorsten Scherler added a comment - The last attachment core.target.diff (65 kb) is a refactoring of all core targets. Since this patch will break a lot of build systems that are using the old targets we need to reach a decision how to we apply the patches to close this issue.
          Hide
          Vadim Gritsenko added a comment -
          As an alternative solution, you guys can recommend following usage of forrest from ant:

              <target name="site">
                  <exec command="${forrest.home}/bin/forrest"/>
              </target>

          Seems to be working for me. (PS sorry for butting in into jira discussion, i'm not subbed to forrest mail lists :)
          Show
          Vadim Gritsenko added a comment - As an alternative solution, you guys can recommend following usage of forrest from ant:     <target name="site">         <exec command="${forrest.home}/bin/forrest"/>     </target> Seems to be working for me. (PS sorry for butting in into jira discussion, i'm not subbed to forrest mail lists :)
          Hide
          Vadim Gritsenko added a comment -
          Jumped the gun too quickly... *Almost* working - something like projectInfo plugin was not found or some such. Probably it won't work in windows, too...
          Show
          Vadim Gritsenko added a comment - Jumped the gun too quickly... *Almost* working - something like projectInfo plugin was not found or some such. Probably it won't work in windows, too...

            People

            • Assignee:
              Unassigned
              Reporter:
              Nick Chalko
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Development