IMO this isn't necessary. We already control whether we deploy the myfaces jars using a profile. Can't we add a profile which includes the JSTL jars in the demo when it's built? Also, it should be easy enough to add them to tomcat as a shared library as well.

Scott

Paul Spencer wrote:
The current Trinidad demo will not work in a non-J2EE container, i.e. Tomcat 6.0, because it does not contain the JSTL jar. Should we add a non-J2EE demo to the distribution?

I would say yes because it simplifies the process of getting the demo running in an not-J2EE environment.

Paul Spencer

Reply via email to