Not exactly. I'm not using sysdeo's tomcat, just Eclipse WST with a Server configured, and it deploys my app by copying all the files inside tomcat (it also configures a default context). The problem is that the provided-scope jars get copyied too by eclipse and they shouldn't (a good example is servlet-api.jar, its required to compile but shouldn't be deployed). It seems that there is a workaround using sysdeo... the fact is that im using a local tomcat and its easier using eclipse WST for make deploys in this case, i think...
Thanks anyway!! 2007/10/2, Jim Sellers <[EMAIL PROTECTED]>: > Is this your issue? > http://jira.codehaus.org/browse/MECLIPSE-79 > > HTH > Jim > > > On 10/2/07, Juan Ignacio Garzón <[EMAIL PROTECTED]> wrote: > > > > Hi, I'm using m2eclipse 0.0.10, Eclipse 3.3.0, Maven 2.0.7. > > > > I have added some maven dependencies using a "provided" scope: > > > > <dependency> > > <groupId>pae</groupId> > > <artifactId>library</artifactId> > > <version>1.0</version> > > <scope>provided</scope> <--- this line > > </dependency> > > > > But,the problem is, that when I publish my site using eclipse, that > > dependency get's deployed, because all the jars inside "Maven2 > > Dependencies module" are deployed, and I couldnt find a way to filter > > some of them. > > > > Thanks! > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
