What if there is a need for a different JAR for different facelets versions? For example, if Jacob changed the tag handler API in Facelets 1.2, then the code would be different for Facelets 1.1 and 1.2. This is the big reason I see for having the Jars separate.

-Andrew

On 5/15/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
> I don't see these as significant advantages to making it a separate
> JAR.  None of these should be marked as required dependencies for
> standard tomahawk use - they should all be marked as "provided"
> scope, which avoids the issue.

I agreee. Why not include the facelets config file in the META-INF of
the regular old tomahawk.jar?  It certainly doesn't hurt anyone not
using facelets and it would be a major incentive to use MyFaces
components if they were able to be used with facelets out of the box.

> -- Adam

Sean

Reply via email to