Sure :-) the two goals here are to save time but also to make sure the person who follows this guide after me saves even more time :-)
On 5/22/08, Eugene Kuleshov <[EMAIL PROTECTED]> wrote: > Murray Waters wrote: >> I no longer thing it is necessary - i've removed it. >> >> Can it be replaced with a recommendation to add >> >> <dependency> >> <groupId>org.apache.tomcat</groupId> >> <artifactId>jsp-api</artifactId> >> <version>6.0.16</version> >> <scope>provided</scope> >> </dependency> >> <dependency> >> <groupId>org.apache.tomcat</groupId> >> <artifactId>servlet-api</artifactId> >> <version>6.0.16</version> >> <scope>provided</scope> >> </dependency> >> >> As igor suggested to me? >> >> The goal is to get a working tomcat + WTP development environment up >> and going as quick as possible. You can't go ahead and do a lot of >> JSP/Servlet stuff without specifying your dependencies on servlet-api >> and jsp-api, you won't get very far writing even the simplest of >> applications. >> >> I think it would be relevant in the context of this tutorial because >> its not immediately clear how to do this the "eclipse+ maven + >> m2eclispe +wtp way" and it took me about 2 days to figure this out :-). > Yes, this is how it should work from Maven. Would be great if you can > test it on your projects and update wiki page with above or similar > snippet. Though it may make sense to use non-tomcat artifacts, e.g. > javax.servlet:servlet-api:2.4 and javax.servlet:jsp-api:2.0 (you can > also use Ctrl-1 quickfix on missing classes in the Java editor to search > them in Maven). > > Also, please don't hesitate to ask questions. It may really help you > to save some time. :-) > > regards, > Eugene > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Sent from Gmail for mobile | mobile.google.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
