[
https://issues.apache.org/jira/browse/EXTVAL-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040261#comment-13040261
]
Matt Benson commented on EXTVAL-133:
------------------------------------
Yes, I actually intended this issue as more a stepping-stone to a full-fledged
"test extval on the 2.0 branch" issue, wherein I could submit the tweak as a
patch against trunk. However, I can also submit the 2.0 version of the patch.
> tests in
> test-modules/core-tests/src/test/java/org/apache/myfaces/extensions/validator/test/core/stage
> should customize servletContext as part of setup
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: EXTVAL-133
> URL: https://issues.apache.org/jira/browse/EXTVAL-133
> Project: MyFaces Extensions Validator
> Issue Type: Test
> Affects Versions: 2.0.5
> Reporter: Matt Benson
> Assignee: Rudy De Busscher
> Attachments: EXTVAL-133.patch.txt
>
>
> these tests work in trunk, but when running them against
> https://svn.apache.org/repos/asf/myfaces/extensions/validator/branches/branch_for_jsf_2_0,
> they fail because the DefaultELHelper requests the ProjectStage so that it
> is cached before the testcase has the chance to add the
> "javax.faces.PROJECT_STAGE" init parameter. The attached patch continues to
> test successfully against trunk _and_ (with the minor tweak of a custom
> ProjectStageResolver for the CustomProjectStageTestCase) works for JSF 2.0 .
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
