[
http://jira.codehaus.org/browse/MECLIPSE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95326
]
Martin Goldhahn commented on MECLIPSE-79:
-----------------------------------------
The scope "provided" is needed in the pom for javax.servlet. Otherwise you
cannot compile the project. "provided" prevents the artifact from being
included in the package. Sysdeo's Tomcat plugin uses a special classloader
(DevClassLoader) to include all project dependencies in the context's
classpath. Since Tomcat plugin version 3.2 beta3 the plugin contains an
extended property page for the DevLoader. (The latest release is 3.2 which was
relesed after beta3). The extended property page allows you to exclude certain
jar files from the DevLoaders classpath. This is the place where you remove the
check mark on the javax.servlet API jar file. If you use the Maven plugin for
Eclipse (which is not the same as the maven plugin maven-eclipse-plugin) You
also need to uncheck the Maven classpath container.
Here the short versjon:
- in the POM: servlet-api artifact with scope provided
- uncheck servlet-api.jar in the DevLoader's property page
> exclude dependencies from the Classpath Container
> -------------------------------------------------
>
> Key: MECLIPSE-79
> URL: http://jira.codehaus.org/browse/MECLIPSE-79
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Environment: Windows, Eclipse 3.1.2
> Reporter: Martin Goldhahn
> Attachments: MECLIPSE-79.patch
>
>
> There are some dependencies that need to be in the POM in order to compile
> the project (e.g. javax.servlet). When I use Sysdeo's Tomcat plugin, I get an
> error because the servlet classes from the POM are included in the classpath
> via the classpath container.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
