the myfaces-api is the ASF impl of javax.faces.*.
But otoh the JSF api design makes the api depending on small internal classes which make the myfaces-api work with just the myfaces-impl. Same with Mojarra. At least that was the case the last time I tried that shortly ;) Of course you can run apps which are compiled against the myfaces-api also with mojarra and vice versa. Thus I'd say you can include it IF you don't want to be able to run Mojarra on tomee instead of MyFaces. LieGrue, strub ----- Original Message ----- > From: Matt Benson <[email protected]> > To: MyFaces Development <[email protected]> > Cc: > Sent: Friday, October 28, 2011 9:53 PM > Subject: Re: Inclusion of MyFace API in javaee-api jar > > On Fri, Oct 28, 2011 at 2:46 PM, David Blevins <[email protected]> > wrote: >> Quick question on the org.apache.myfaces.core:myfaces-api jar. >> >> Is it tied to MyFaces in some way? Guessing the answer is, yes, as it is > labeled "myfaces-api" and not something more generic like > "faces-api" >> >> If the answer is, no, then the follow up is how often does its contents > change? >> >> If it is stable and only changed once in a while, we might include it in > the javaee-api jar we produce from OpenEJB/TomEE. We don't include JavaMail > for example as it really isn't an API but an actual implementation. Seems > like that is the case here. > > Nail on the head and all that. :) > > Matt > >> >> >> -David >> >> >
