That "Should" be all you need... A friend of mine verified on Tomcat as well. Perhaps you did something different, Jim?
I think I've been able to do JSF 2.0 and Tomcat with the following:
<dependencies>
<dependency>
<groupId>javax.faces</groupId>
<artifactId>jsf-api</artifactId>
<version>2.0</version>
</dependency><version>2.0.2</version>
<dependency>
<groupId>com.sun.faces</groupId>
<artifactId>jsf-impl</artifactId>
</dependency>
</dependencies>
<repositories>
<repository>
<id>maven2-repository.dev.java.net</id>
<name>Java.net Repository for Maven</name>
</repositories>
On Jan 26, 2010, at 1:24 PM, Jim Driscoll wrote:
> Wonderful news. Glad that's settled out.
>
> While I'm thinking of it, there's a change that I'd like to see on the dependencies section at http://www.javaserverfaces.org/download
>
> The dependencies aren't nearly as clearcut as you have listed, sadly. In particular, they don't work for Tomcat.
>
> For the demos, I used the following code block:
>
> <repositories>
> <repository>
> <id>java.net.m2</id>
> <name>java.net m2 repo</name>
> <url>http://download.java.net/maven/2</url>
> </repository>
> <repository>
> <id>glassfish-repo-archive</id>
> <name>Nexus repository collection for Glassfish</name>
> <url>http://maven.glassfish.org/content/groups/glassfish</url>
> </repository>
> <repository>
> <id>ibiblio.mirrors</id>
> <url>http://mirrors.ibiblio.org/pub/mirrors/maven2</url>
> </repository>
> <repository>
> <id>codehaus</id>
> <name>codehaus</name>
> <url>http://repository.codehaus.org</url>
> </repository>
> </repositories>
>
> <dependencies>
> <dependency>
> <groupId>javax.faces</groupId>
> <artifactId>jsf-api</artifactId>
> <version>2.0</version>
> <scope>provided</scope>
> </dependency>
>
> <!--
> Uncomment these dependencies and comment out the one above to use
> a simple servlet container instead of a Java EE Application Server
> <dependency>
> <groupId>com.sun.faces</groupId>
> <artifactId>jsf-api</artifactId>
> <version>[2.0.1,)</version>
> </dependency>
> <dependency>
> <groupId>com.sun.faces</groupId>
> <artifactId>jsf-impl</artifactId>
> <version>[2.0.1,)</version>
> </dependency>
> <dependency>
> <groupId>javax.servlet</groupId>
> <artifactId>servlet-api</artifactId>
> <version>2.5</version>
> <scope>provided</scope>
> </dependency>
> <dependency>
> <groupId>javax.servlet.jsp</groupId>
> <artifactId>jsp-api</artifactId>
> <version>2.1</version>
> <scope>provided</scope>
> </dependency>
> <dependency>
> <groupId>javax.servlet.jsp.jstl</groupId>
> <artifactId>jstl-api</artifactId>
> <version>1.2</version>
> </dependency>
> <dependency>
> <groupId>org.glassfish.web</groupId>
> <artifactId>jstl-impl</artifactId>
> <version>1.2</version>
> </dependency>
> -->
>
> </dependencies>
>
>
> Yeah, Sun's repos are a mess. The complexity is really only needed for Tomcat/Jetty deployments.
>
> You can find the demo's pom.xml at
> https://mojarra.dev.java.net/source/browse/*checkout*/mojarra/trunk/jsf-demo/helloworld/pom.xml?content-type=text%2Fplain&rev=8105
>
> Jim
>
> On 1/25/10 11:16 PM, Kito Mann wrote:
>> Hey guys,
>>
>> javaserverfaces.org <http://javaserverfaces.org> and javaserverfaces.com
>> <http://javaserverfaces.com> now officially redirect to
>> http://www.javaserverfaces.org. It's old-school: the JSF Central web app
>> has a filter that just does a redirect for those two domains. It's good
>> enough for now, though. Once we're running on a more flexible platform,
>> we can just point the CNAME record directly at the correct IP.
>> ---
>> Kito D. Mann | twitter: kito99 | Author, JSF in Action
>> Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting
>> http://wwwJSFCentral.com - JavaServer Faces FAQ, news, and info |
>> twitter: jsfcentral
>> +1 203-404-4848 x3
>>
>> Sign up for the JSFCentral newsletter: http://oi.vresp.com/?fid=ac048d0e17
>>