Carlin-- These changes sound fine to me. To be clear, is the reason to update MyFaces just to use a newer release?
With respect to JSF 1.2, MyFaces hasn't delivered official release that supports this version of the specification; according to their most recent status report, this should be done sometime in the first quarter, though testing could be done against builds -- assuming they exist. :) A discussion on JEE 5 support would be great! Eddie On 1/23/07, Carlin Rogers <[EMAIL PROTECTED]> wrote:
I'd like to update the netui-jsf sample build.xml and build.properties files to support building with newer 1.1.x versions of MyFaces. There are a couple of issues that I've noticed with the netui-jsf sample. First, it assumes a file naming convention for MyFaces jars that is no longer used (since 1.1.2). The build properties file only uses a directory location and assumes the jar names will not change from release to release of the JSF implementations. Also, later 1.1.x releases of MyFaces are dependent on commons-lang.jar. Does anyone mind if I modify the build.xml and build.properties in the netui-jsf sample to support newer 1.1.x versions of MyFaces? NOTE - this is not an effort to test and support the 1.2 version of MyFaces and the JSF 1.2 spec. I can kick off a separate thread about JSF 1.2 support (and JEE 5) a little later. Also, to make sure the distribution builds correctly with the sample, I will update the netui/external/jsf dir to include MyFaces 1.1.4. The current version we use for builds and tests is an old MyFaces 1.0.9. Sound OK? Thanks, Carlin
