]
Ryan Bradley commented on FORGE-390:
------------------------------------
At the time, I ended up creating a new project and copying my plugin's content over as
a workaround, and that worked fine. The bug hasn't occurred since then, so I
don't think it's an issue unless more people begin to have this problem.
Plugin builds successfully but cannot be executed
-------------------------------------------------
Key: FORGE-390
URL:
https://issues.jboss.org/browse/FORGE-390
Project: Forge
Issue Type: Bug
Components: Plugin API, Usability
Affects Versions: 1.0.0.Beta3
Environment: OS: Fedora 15, JPA Provider: Hibernate 4.0.0.CR6, Container: JBoss
AS 7.0.3.Final
Reporter: Ryan Bradley
My plugin, created and developed in Forge, stopped being recognized by Forge. I tried
removing the plugin from .forge/plugins/installed.xml, running 'forge source-plugin
${PATH_TO_PLUGIN}' again, confirming that it had been added to installed.xml again,
and, although the build was successful, when I tried to execute the plugin, the command
was not found. A pastebin of the build and subsequent attempted execution is provided at:
http://pastebin.com/5us0GAMP. (Yes, I did double check that I used the same name as the
plugin alias). Perhaps this could be a problem with the Forge plugin setup process?
Note: as a workaround, I had to create a new plugin and copy over source code from the
previous plugin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: