[size=large]Classpath entry org.maven.eclipse.MAVEN2_CLASSPATH_CONTAINER will not be exported or published[/size]
[size=medium]Eclipse警告:[/size]
[size=small] 且启动服务器时,将抛出无法加载Maven所管理jar包的异常。[/size]
[size=medium]原因:[/size]
[size=small] 打包时并没有将Maven管理的jar包成功写入war包,导致部署的项目所需jar包缺失,所以会引起异常。[/size]
[size=medium]解决方案:[/size]
[size=small] 在项目的根目录下找到这个.classpath文件,如下[/size]
[img]http://dl2.iteye.com/upload/attachment/0123/8269/43468e27-694e-39cb-a6b2-811c9dd984fb.jpg[/img]
[size=small] 然后打开编辑,找到以下标签元素,然后添加下面注释之间的内容[/size]
[size=small] 接下来在Eclipse中选中项目,右键选择Build Path->Configure Build Path[/size]
[img]http://dl2.iteye.com/upload/attachment/0123/8271/bf492953-33f1-3b03-959c-5d3e0814227d.jpg[/img]
[size=small] 然后在这个弹出框内找到Order and Export栏,勾选Maven Dependencies然后点击OK[/size]
[img]http://dl2.iteye.com/upload/attachment/0123/8273/d468ef20-e854-3233-b613-639b98121d61.jpg[/img]
[size=small] 接下来,清理构建重新部署,再启动服务器,就不会抛出之前的异常了。当然,Eclipse的警告也随之消除。[/size]
[size=medium]Eclipse警告:[/size]
Classpath entry org.maven.eclipse.MAVEN2_CLASSPATH_CONTAINER will not be exported or published
[size=small] 且启动服务器时,将抛出无法加载Maven所管理jar包的异常。[/size]
[size=medium]原因:[/size]
[size=small] 打包时并没有将Maven管理的jar包成功写入war包,导致部署的项目所需jar包缺失,所以会引起异常。[/size]
[size=medium]解决方案:[/size]
[size=small] 在项目的根目录下找到这个.classpath文件,如下[/size]
[img]http://dl2.iteye.com/upload/attachment/0123/8269/43468e27-694e-39cb-a6b2-811c9dd984fb.jpg[/img]
[size=small] 然后打开编辑,找到以下标签元素,然后添加下面注释之间的内容[/size]
<classpathentry kind="con" path="org.eclipse.m2e.MAVEN2_CLASSPATH_CONTAINER">
<attributes>
<attribute name="maven.pomderived" value="true"/>
<!-- 添加部分 -->
<attribute name="org.eclipse.jst.component.dependency" value="/WEB-INF/lib"/>
<!-- 添加部分 -->
</attributes>
</classpathentry>
[size=small] 接下来在Eclipse中选中项目,右键选择Build Path->Configure Build Path[/size]
[img]http://dl2.iteye.com/upload/attachment/0123/8271/bf492953-33f1-3b03-959c-5d3e0814227d.jpg[/img]
[size=small] 然后在这个弹出框内找到Order and Export栏,勾选Maven Dependencies然后点击OK[/size]
[img]http://dl2.iteye.com/upload/attachment/0123/8273/d468ef20-e854-3233-b613-639b98121d61.jpg[/img]
[size=small] 接下来,清理构建重新部署,再启动服务器,就不会抛出之前的异常了。当然,Eclipse的警告也随之消除。[/size]