Oh, also, for an example of adding classes to the deployment, see the
PrettyFaces Forge Plugin:
https://github.com/ocpsoft/prettyfaces-forge-plugin/blob/master/src/test/...
The @Deployment method overrides and extends the default deployment.
~Lincoln
On Sun, Oct 30, 2011 at 1:27 PM, Lincoln Baxter, III <
lincolnbaxter(a)gmail.com> wrote:
Hey Richard,
Plugins aren't loaded by the test-harness. In order to do this, you'll
have to add the classes to the Arquillian deployment manually. Just curious
- Are you planning on using RichFaces in the generated pages? If possible,
I'd like to avoid this for default setup, since even RichFaces is not
technically "plain Java EE" - as an extension, that's fine, but we need to
be able to output a POJEE project :)
I hope this does not throw too much of a wrinkle into anything!
~Lincoln
On Sun, Oct 30, 2011 at 1:48 AM, Richard Kennard <
richard(a)kennardconsulting.com> wrote:
> Hi guys,
>
> When running my unit tests through Forge test-harness, how should I add
> RichFaces to my project? Doing...
>
> Project project = setupScaffoldProject();
> getShell().execute("richfaces setup");
>
> ...does not seem to work?
>
> Regards,
>
> Richard.
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/forge-dev
>
--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"