<p dir="ltr">I found the reason and provided you a PR: <a href="https://github.com/ivannov/core/pull/1">https://github.com/ivannov/core/pull/1</a></p>
<p dir="ltr">The problem was that no container was specified to load the addon, therefore Forge loads your addon as a library addon only (without any services).</p>
<p dir="ltr">I have also provided a test case for you to keep on rocking ;)<br></p>
<p dir="ltr">Enjoy!</p>
<div class="gmail_quote">Em 09/12/2015 19:54, "Ivan St. Ivanov" <<a href="mailto:ivan.st.ivanov@gmail.com">ivan.st.ivanov@gmail.com</a>> escreveu:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi George,<div><br></div><div>I am now working on the <a href="https://issues.jboss.org/browse/FORGE-2545" target="_blank">testing addon</a>. I started my work on it a couple of weeks ago, developing against Forge 2. But after Forge 3 was moved to master, I changed my addon accordingly.</div><div><br></div><div>Unfortunately, now after I build and install it, it doesn't work anymore. I mean, the command testing-setup is not available neither in the IDE, nor in the shell. Most probably I am missing some dependencies, I don't know. But it was working fine while built against Forge 2.</div><div><br></div><div>Here is the Forge Core code together with my addon:</div><div><br></div><div><a href="https://github.com/ivannov/core/tree/FORGE-2545" target="_blank">https://github.com/ivannov/core/tree/FORGE-2545</a><br></div><div><br></div><div>The addon itself is here:</div><div><br></div><div><a href="https://github.com/ivannov/core/tree/FORGE-2545/testing" target="_blank">https://github.com/ivannov/core/tree/FORGE-2545/testing</a><br></div><div><br></div><div>i will be very happy if you point me to what I am doing wrong :)</div><div><br></div><div>Thanks,</div><div>Ivan</div><div><br></div></div>
</blockquote></div>