[forge-issues] [JBoss JIRA] (FORGE-434) Inclusion of Seam Render Module: Conflict with Forge Core

[Lincoln Baxter III (JIRA)]

     [ https://issues.jboss.org/browse/FORGE-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lincoln Baxter III resolved FORGE-434.
--------------------------------------

         Assignee: Lincoln Baxter III  (was: Koen Aers)
    Fix Version/s: 1.0.0.CR1
       Resolution: Done


Ok. Please test with latest forge SNAPSHOT source build. This should be resolved (also please update your plugin from github. I've made some changes there, too)

~Lincoln
                
> Inclusion of Seam Render Module: Conflict with Forge Core
> ---------------------------------------------------------
>
>                 Key: FORGE-434
>                 URL: https://issues.jboss.org/browse/FORGE-434
>             Project: Forge
>          Issue Type: Bug
>          Components: Forge Build, JBoss Tools Integration, Plugin API
>    Affects Versions: 1.0.0.Beta3, 1.0.0.Beta4, 1.0.0.Beta5
>         Environment: Fedora 15, 64-bit: exists with Forge versions 1.0.0.Beta3 through 1.0.0.Beta5
>            Reporter: Ryan Bradley
>            Assignee: Lincoln Baxter III
>             Fix For: 1.0.0.CR1
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira