You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2007/08/14 22:11:47 UTC

[jira] Commented: (MECLIPSE-284) Transitive dependencies with scope provided should not be part of .classpath file

    [ http://jira.codehaus.org/browse/MECLIPSE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104858 ] 

John Casey commented on MECLIPSE-284:
-------------------------------------

Can you please provide any changes as a unified diff, so we can isolate the changed lines? This works much better as these files age, and gives us a much more focused idea of what you've done.

Also, please provide some sort of test case that will fail prior to your fix, and pass afterwards.

> Transitive dependencies with scope provided should not be part of .classpath file
> ---------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-284
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-284
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>          Components: dependency resolution
>    Affects Versions: 2.3
>         Environment: Windows XP
>            Reporter: Jan Dieckmann
>         Attachments: AbstractIdeSupportMojo.java
>
>
> We are using the maven eclipse plugin and it does a very good job for us. Úsing the plugin we now have the pom's as the sole source for all .classpath and .project files in our multi module project. We really appreciate this solution. The maven eclipse plugin does a lot for us .. actually it does too much.
> Some of our dependencies have a scope of "provided". The default maven behaviour is to ignore those items when transitive dependencies are resolved. The plugin's behaviour is different and there is no configuration to switch to the default behaviour. At least we did not find one. As a result our .classpath files have a lot of unnecessary references to jar files.
> We changed the class AbstractIdeSupportMojo.java to get rid of dispensable jars. The inner class IVUScopeFilter does the job. This class is used in the method call artifactCollector.collect().
> Is there something we missed or should the plugin be changed in a way we did?
> best regards
> Jan Dieckmann

-- 
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