Uploaded image for project: 'Forge'
  1. Forge
  2. FORGE-434

Inclusion of Seam Render Module: Conflict with Forge Core

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.0.0.CR1
    • 1.0.0.Beta3, 1.0.0.Beta4, 1.0.0.Beta5
    • Plugin API
    • None
    • Hide

      To reproduce this bug, it is important to use a plugin which uses seam-render. As an example, you can use my plugin, available at: https://github.com/forge/plugin-spring-mvc.

      Then, navigate to the plugin's home folder, start Forge, and execute 'forge source-plugin .' Forge should indicate that the build and installation were performed successfully. However, when you try to execute the 'spring' command (the plugin's main command), it will output an error that no such command exists. The only workaround is the manual inclusion of 'org.jboss.seam.render', as described earlier in this report.

      Show
      To reproduce this bug, it is important to use a plugin which uses seam-render. As an example, you can use my plugin, available at: https://github.com/forge/plugin-spring-mvc . Then, navigate to the plugin's home folder, start Forge, and execute 'forge source-plugin .' Forge should indicate that the build and installation were performed successfully. However, when you try to execute the 'spring' command (the plugin's main command), it will output an error that no such command exists. The only workaround is the manual inclusion of 'org.jboss.seam.render', as described earlier in this report.
    • Workaround Exists
    • Hide

      A workaround exists by adding the following module to the dependencies of that particular build's module.xml file:

      <module name="org.jboss.seam.render" services="import"/>

      Show
      A workaround exists by adding the following module to the dependencies of that particular build's module.xml file: <module name="org.jboss.seam.render" services="import"/>

      I am developing a plugin which depends on the seam-render module. When I execute 'forge source-plugin' to build and install the plugin, both operations are successful. Forge outputs "Build successful", and then, "Installed from [

      {plugin.home}

      ] successfully." However, whenever I try to execute the plugin, Forge outputs the following error: "ERROR: No such command

      {command.name}

      ". Through debugging, I have determined that it is the inclusion of the seam-render JAR in my plugin (also part of the Forge core) which causes these build issues. A workaround, described below, exists by manually including it as a dependency of the plugin, but this is obviously not ideal for third-party users of the plugin.

              lincolnthree Lincoln Baxter III (Inactive)
              ryanbradley_jira Ryan Bradley (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: