[
http://jira.codehaus.org/browse/MECLIPSE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177135#action_177135
]
Jim Sellers commented on MECLIPSE-565:
--------------------------------------
Found a workaround:
"As a workaround these warnings can be filtered out by removing selection from
"Classpath Dependency Validator Message" in Problems view filter configuration."
http://code.google.com/p/q4e/issues/detail?id=162
> Classpath entries to be marked as NOT exported
> ----------------------------------------------
>
> Key: MECLIPSE-565
> URL: http://jira.codehaus.org/browse/MECLIPSE-565
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: Core : Dependencies resolution and build path
> (.classpath)
> Affects Versions: 2.6
> Reporter: Jim Sellers
>
> This is the other side of the MECLIPSE-230.
> In my war project, for all the jar's that are provided, test, or otherwise
> NOT to be exported, eclipse complains with a warning:
> "Classpath entry M2_REPO/junit/junit/4.4/junit-4.4.jar will not be exported
> or published. Runtime ClassNotFoundExceptions may result."
> The work around is the "quick fix", but that means that you have to do this
> every time you run eclipse:eclipse.
> The fix would be to add that it is a non-dependency:
> <classpathentry kind="var" path="M2_REPO/junit/junit/4.4/junit-4.4.jar"
> sourcepath="M2_REPO/junit/junit/4.4/junit-4.4-sources.jar">
> <attributes>
> <attribute
> name="org.eclipse.jst.component.nondependency" value=""/>
> </attributes>
> </classpathentry>
--
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
