I guess it depends what you are going to do with it. It should be fine as a compile-time dependency for code referencing JSF classes. But you wouldn't want to use it at runtime with a different JSF implementation or even a different myfaces implementation. It should be fine for a javaee-api jar as a compile-time reference, but not for a javaee-imp.jar. I think it's exactly the same as including a servlet api jar.
On Fri, Oct 28, 2011 at 3: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. > > > -David > >
