Hi Reading the manifest depends on who build it, so that may break quickly
I think a better approach is to create small utility that looks for the few (two?) implementations of a given class that has distinct characteristics for the different versions of the api. Hermod -----Opprinnelig melding----- Fra: Gary VanMatre [mailto:[EMAIL PROTECTED] Sendt: 6. mars 2007 17:16 Til: dev@shale.apache.org Emne: Determining the flavor of the JSF runtime I've been trying to determine a better strategy for detecting the supplier and version of the JSF runtime. This has to do with a open JIRA ticket [1]. I attempted to create a utility class to determine the implementor of the runtime and the JSF spec version [2]. This was a real hack but I didn't see a better way and I'm still not sure the best way to dynamically extract this version information. Besides knowing the JSF version (1.1, 1.2), we need the implementation version (myfaces 1.1, 1.3...). I was thinking about trying to read the manifest but haven't figured out a good method. This seems like it should be part of the JSF API? Any ideas? Gary [1] https://issues.apache.org/struts/browse/SHALE-418 [2] https://svn.apache.org/viewvc/shale/framework/trunk/shale-clay/src/main/java /org/apache/shale/clay/utils/JSFRuntimeTracker.java?view=markup
