Details

      Description

      Apache Gump has trouble finding our plugins.

        Issue Links

          Activity

          Hide
          David Crossley added a comment -
          See our http://forrest.apache.org/gump.html

          The "forrest-core" has been building properly for some time now.
          Also "forrest-test-basic" builds properly. It builds a simple site with no plugins, so just exercises the core of Forrest.

          However the "forrest-test" has some strange issue finding the plugins. Follow the link to the "vmgump.a.o" reports. The nag emails are coming only to me at this stage.
          Show
          David Crossley added a comment - See our http://forrest.apache.org/gump.html The "forrest-core" has been building properly for some time now. Also "forrest-test-basic" builds properly. It builds a simple site with no plugins, so just exercises the core of Forrest. However the "forrest-test" has some strange issue finding the plugins. Follow the link to the "vmgump.a.o" reports. The nag emails are coming only to me at this stage.
          Hide
          David Crossley added a comment -
          Comparing the local running of '$FORREST_HOME/main/build.sh test' with Gump output around the stage where it tries to find the first plugin "output.pdf" for the first test site "skinned".

          (Note that need to edit build.sh first to disable the "-logger org.apache.tools.ant.NoBannerLogger" to get comparable output to Gump which just executes our ant target "test" i.e. no logger set.)

          Here is the snippet from the local build output:
          ----------
          ...
          fetch-plugin:
          Trying to find the description of org.apache.forrest.plugin.output.pdf in the different descriptor files
          Using the descriptor file /Users/me/Documents/svn/asf/forrest/build/test_skinned_site/build/tmp/plugins-1.xml...
          Processing /Users/me/Documents/svn/asf/forrest/build/test_skinned_site/build/tmp/plugins-1.xml to /Users/me/Documents/svn/asf/forrest/build/test_skinned_site/build/tmp/pluginlist2fetchbuild.xml
          Loading stylesheet /Users/me/Documents/svn/asf/forrest/main/var/pluginlist2fetch.xsl

          fetch-local-unversioned-plugin:

          get-local:
          Trying to locally get org.apache.forrest.plugin.output.pdf
          Looking in local /Users/me/Documents/svn/asf/forrest/plugins
          Found !

          init-build-compiler:

          echo-init:

          init:

          compile:

          jar:

          local-deploy:
          Locally deploying org.apache.forrest.plugin.output.pdf
          Copying 33 files to /Users/me/Documents/svn/asf/forrest/build/plugins/org.apache.forrest.plugin.output.pdf
          Copying 1 file to /Users/me/Documents/svn/asf/forrest/build/plugins
          Copying 5 files to /Users/me/Documents/svn/asf/forrest/build/plugins/lib

          build:
          Plugin org.apache.forrest.plugin.output.pdf deployed ! Ready to configure

          fetch-remote-unversioned-plugin-version-forrest:

          fetch-remote-unversioned-plugin-unversion-forrest:

          has-been-downloaded:

          downloaded-message:

          uptodate-message:

          not-found-message:
          Fetch-plugin Ok, installing !

          unpack-plugin:

          install-plugin:

          configure-plugin:

          configure-output-plugin:
          Mounting output plugin: org.apache.forrest.plugin.output.pdf
          ...
          ... and more configuration of that plugin.
          ----------

          So via local build, it finds the plugin in the local "plugins" directory and installs and configures it properly.

          Here is the corresponding snippet from the Gump build output:
          ----------
          ...
          fetch-plugin:
               [echo] Trying to find the description of org.apache.forrest.plugin.output.pdf in the different descriptor files
               [echo] Using the descriptor file /srv/gump/public/workspace/forrest/build/test_skinned_site/build/tmp/plugins-1.xml...
               [xslt] Processing /srv/gump/public/workspace/forrest/build/test_skinned_site/build/tmp/plugins-1.xml to /srv/gump/public/workspace/forrest/build/test_skinned_site/build/tmp/pluginlist2fetchbuild.xml
               [xslt] Loading stylesheet /srv/gump/public/workspace/forrest/main/var/pluginlist2fetch.xsl

          fetch-local-unversioned-plugin:
               [echo] Fetch-plugin Ok, installing !

          unpack-plugin:

          install-plugin:

          configure-plugin:
               [echo] No locationmap provided for plugin org.apache.forrest.plugin.output.pdf
          ...
          ... and it stops "configuring" there, not realising that it has failed.
          ----------

          So via Gump, it thinks that it has found the plugin (but installed nothing) and goes on to build the site, failing with the PDFs.
          Show
          David Crossley added a comment - Comparing the local running of '$FORREST_HOME/main/build.sh test' with Gump output around the stage where it tries to find the first plugin "output.pdf" for the first test site "skinned". (Note that need to edit build.sh first to disable the "-logger org.apache.tools.ant.NoBannerLogger" to get comparable output to Gump which just executes our ant target "test" i.e. no logger set.) Here is the snippet from the local build output: ---------- ... fetch-plugin: Trying to find the description of org.apache.forrest.plugin.output.pdf in the different descriptor files Using the descriptor file /Users/me/Documents/svn/asf/forrest/build/test_skinned_site/build/tmp/plugins-1.xml... Processing /Users/me/Documents/svn/asf/forrest/build/test_skinned_site/build/tmp/plugins-1.xml to /Users/me/Documents/svn/asf/forrest/build/test_skinned_site/build/tmp/pluginlist2fetchbuild.xml Loading stylesheet /Users/me/Documents/svn/asf/forrest/main/var/pluginlist2fetch.xsl fetch-local-unversioned-plugin: get-local: Trying to locally get org.apache.forrest.plugin.output.pdf Looking in local /Users/me/Documents/svn/asf/forrest/plugins Found ! init-build-compiler: echo-init: init: compile: jar: local-deploy: Locally deploying org.apache.forrest.plugin.output.pdf Copying 33 files to /Users/me/Documents/svn/asf/forrest/build/plugins/org.apache.forrest.plugin.output.pdf Copying 1 file to /Users/me/Documents/svn/asf/forrest/build/plugins Copying 5 files to /Users/me/Documents/svn/asf/forrest/build/plugins/lib build: Plugin org.apache.forrest.plugin.output.pdf deployed ! Ready to configure fetch-remote-unversioned-plugin-version-forrest: fetch-remote-unversioned-plugin-unversion-forrest: has-been-downloaded: downloaded-message: uptodate-message: not-found-message: Fetch-plugin Ok, installing ! unpack-plugin: install-plugin: configure-plugin: configure-output-plugin: Mounting output plugin: org.apache.forrest.plugin.output.pdf ... ... and more configuration of that plugin. ---------- So via local build, it finds the plugin in the local "plugins" directory and installs and configures it properly. Here is the corresponding snippet from the Gump build output: ---------- ... fetch-plugin:      [echo] Trying to find the description of org.apache.forrest.plugin.output.pdf in the different descriptor files      [echo] Using the descriptor file /srv/gump/public/workspace/forrest/build/test_skinned_site/build/tmp/plugins-1.xml...      [xslt] Processing /srv/gump/public/workspace/forrest/build/test_skinned_site/build/tmp/plugins-1.xml to /srv/gump/public/workspace/forrest/build/test_skinned_site/build/tmp/pluginlist2fetchbuild.xml      [xslt] Loading stylesheet /srv/gump/public/workspace/forrest/main/var/pluginlist2fetch.xsl fetch-local-unversioned-plugin:      [echo] Fetch-plugin Ok, installing ! unpack-plugin: install-plugin: configure-plugin:      [echo] No locationmap provided for plugin org.apache.forrest.plugin.output.pdf ... ... and it stops "configuring" there, not realising that it has failed. ---------- So via Gump, it thinks that it has found the plugin (but installed nothing) and goes on to build the site, failing with the PDFs.
          Hide
          David Crossley added a comment -
          Asked for help at Gump.

          Subject: help with "forrest-test" gump run
          http://s.apache.org/re
          Show
          David Crossley added a comment - Asked for help at Gump. Subject: help with "forrest-test" gump run http://s.apache.org/re
          Hide
          David Crossley added a comment -
          That email discussion explains the problem, and has some things that could be investigated. Thanks.

          In the meantime, i have taken a different approach for Gump. Explicitly deploy the plugins, then force Gump to override Forrest's fancy plugin finding mechanism. This works.
          Show
          David Crossley added a comment - That email discussion explains the problem, and has some things that could be investigated. Thanks. In the meantime, i have taken a different approach for Gump. Explicitly deploy the plugins, then force Gump to override Forrest's fancy plugin finding mechanism. This works.
          Hide
          David Crossley added a comment -
          See r1425266 which added a "gump-plugins" target to our build which deploys the needed plugins. Declare any future others here.

          See r1425427 which forces gump to use those.
          Show
          David Crossley added a comment - See r1425266 which added a "gump-plugins" target to our build which deploys the needed plugins. Declare any future others here. See r1425427 which forces gump to use those.
          Hide
          David Crossley added a comment -
          Fixed. Found a suitable workaround using the "forrest-test-deploy-plugins" gump project.
          Show
          David Crossley added a comment - Fixed. Found a suitable workaround using the "forrest-test-deploy-plugins" gump project.

            People

            • Assignee:
              Unassigned
              Reporter:
              David Crossley
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development