[
https://jira.codehaus.org/browse/MECLIPSE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276917#comment-276917
]
Hans-Peter Störr commented on MECLIPSE-539:
-------------------------------------------
This is indeed quite annoying, since the eclipse classpath gets polluted, you
can accidentially use classes from the runtime deps in the code, and you are in
for surprises if you compile with maven only.
> runtime scope dependencies should not be included into .classpath
> -----------------------------------------------------------------
>
> Key: MECLIPSE-539
> URL: https://jira.codehaus.org/browse/MECLIPSE-539
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: Core : Dependencies resolution and build path
> (.classpath)
> Affects Versions: 2.6
> Environment: maven 2.0.9
> Java 6
> Eclipse 3.4.2
> WinXP
> Reporter: Jean-Paul GUIGUI
>
> "runtime" scope dependencies are today included by "mvn eclipse:eclipse" into
> the .classpath as the other compile dependencies. It should not since it make
> possible to use these runtime dependencies by mistake into Eclipse and then
> write code which is broken the "mvn compile" goal.
> Ideally the "runtime" dependencies should not be included into the
> .classpath, but add only as "User entries" into the "Run configuration ->
> Classpath" of Eclipse
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
