[forge-users] Unable to Inject into Test Class

[Lincoln Baxter, III]

Hey Max,

Interesting. I'm willing to bet this has something to do with the naming
requirements e.g: "groupId:addonId". I'll have to fix this in our
test-runner. Thanks for reporting the fix!

~Lincoln


On Thu, Jan 30, 2014 at 9:13 AM, <forge-users at lists.jboss.org> wrote:

> Hey Lincoln,
>
> I ended up getting the test to work. For the record, here (
> https://github.com/mbarkley/forge-errai/blob/c523efb2c1a114275a8fc8492bbcdd03d126bff4/src/test/java/org/jboss/errai/forge/test/base/ForgeTest.java)
> is the result I ended up with (ignore the classes added to the deployment
> -- those were required to get other test classes extending ForgeTest to
> run).
>
> Note that the last step that was required to get injection working was to
> remove the name (previously "ForgeTest") from the @Deployment annotation.
> It is possible to reproduce the failure by checking out a copy of the
> linked commit, adding "ForgeTest" as the name of the @Deployment, and
> running ForgeTest with JUnit.
>
> Posted by forums
> Original post: https://community.jboss.org/message/855522#855522
> _______________________________________________
> forge-users mailing list
> forge-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-users
>



-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-users/attachments/20140130/fd5dc9c0/attachment.html