Re: [jboss-dev] Why is nekohtml in the main thirdparty?
Test specific jars should be in the testsuite/build-thirdparty.xml so
its clear what is going into the dist vs testsuite dependencies. I
already moved the httpunit componentref there.
Dimitris Andreadis wrote:
Stan added this feature:
http://jira.jboss.com/jira/browse/JBAS-4383
I've completed coding and testing for the flag that allows developers to
package their own JSF impl with their war. So if you add this to your
web.xml:
<context-param>
<param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name>
<param-value>true</param-value>
</context-param>
The built-in JSF impl will not be activated.
The code changes were minimal, but I needed to add four lines to
build/build-thirdparty.xml. These libraries are only there to support
the unit test for this in the testsuite:
+ <componentref name="apache-myfaces" version="1.1.4"/>
+ <componentref name="commons-el" version="1.0"/>
+ <componentref name="httpunit" version="1.6"/>
+ <componentref name="nekohtml" version="0.9.1"/>