[ http://issues.apache.org/struts/browse/SHALE-258?page=comments#action_38220 ] Craig McClanahan commented on SHALE-258: ----------------------------------------
As of the 20060914 nightly build (and corresponding updated 1.0.4-SNAPSHOT), I have completed a first pass at refactoring our build process to address these dependency issues. Now, building the Shale Framework libraries depends on the MyFaces API jar, but when you build an application you still get the choice of which implementation to use. As a side effect, the framework library POMs (including shale-core and shale-test) should no longer force you to use the JSF implementation that they were built against. Leaving the issue open for the moment, because it is very likely I've missed some details along the way. > Shale core and test framework 1.0.3 includes MyFaces 1.1.1 > ---------------------------------------------------------- > > Key: SHALE-258 > URL: http://issues.apache.org/struts/browse/SHALE-258 > Project: Shale > Issue Type: Bug > Components: Core, Test > Affects Versions: 1.0.3-SNAPSHOT, 1.0.3 > Reporter: Paul Spencer > Fix For: 1.0.4-SNAPSHOT > > > Shale's core and test framwork includes MyFaces 1.1.1 in the classpath when > testing via Maven. The testing framework should not impose the JSF > implementation on > what is being tested. > A related issue was reported, and fixed, in MyFaces. See > http://issues.apache.org/jira/browse/TOMAHAWK-612 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
