I'm not sure i understand what you are gaining by upgrading if you ARE NOT going to be using JSF 2. Besides converting it to a maven project, JSF 2 seems like the major gain by upgrading. If its a particular bug you are trying to get around and because very little development is continuing on the Seam Project in general, why not make a custom build to get around any problem and keep the JSF 1.2 in 2.2.x?
Nathan, Thanks for replying. I'm upgrading my current Seam 2.2.1.CR2 app to Seam 2.3.1.Final. And during the upgrade process I noticed Seam 2.3.1 uses JSF2. I would happily use JSF 1.2 if it works with Seam 2.3.1. Which brings me to my original question: does Seam 2.3.1.Final works with JSF 1.2?
Answering my own question here: I managed to run JSF 2.0 with my Seam 2.3.1.Final application. It was a dependency issue which was solved with below dependencies. But now I have a facelets issue which I'm working on.
No it doesn't. One of main reason of releasing 2.3.1 was to support JSF2.
Tomas. Thanks for the reply and answering the question. I have already migrated my application to run with JSF2 and it deploys fine. But I get a runtime exception related to facelets for which I have opened a new discussion at the below link. Thanks again for answering the question.