I was a little surprised that groovy-eclipse bundles servlet-api 2.4 and apparently adds it to the classpath of all Eclipse run configurations. Is this really necessary?
I noticed this with a project which uses a somewhat modern Jetty, which depends on servlet-api 3.0.1 - Unfortunatly, the project cannot be launched from Eclipse anymore, since servlet-api 2.4 ends up on the classpath before servlet-api 3.0.1 and they conflict.
I was a little surprised that groovy-eclipse bundles servlet-api 2.4 and apparently adds it to the classpath of all Eclipse run configurations. Is this really necessary?
I noticed this with a project which uses a somewhat modern Jetty, which depends on servlet-api 3.0.1 - Unfortunatly, the project cannot be launched from Eclipse anymore, since servlet-api 2.4 ends up on the classpath before servlet-api 3.0.1 and they conflict.