[ 
https://issues.apache.org/jira/browse/MECLIPSE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MECLIPSE-284.
-----------------------------------
    Resolution: Won't Fix
      Assignee: Robert Scholte

The Apache Maven team has decided to retire the maven-eclipse-plugin, so this 
issue won't be fixed. 


> Transitive dependencies with scope provided should not be part of .classpath 
> file
> ---------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-284
>                 URL: https://issues.apache.org/jira/browse/MECLIPSE-284
>             Project: Maven Eclipse Plugin (RETIRED)
>          Issue Type: Improvement
>          Components: Core : Dependencies resolution and build path 
> (.classpath)
>    Affects Versions: 2.3
>         Environment: Windows XP
>            Reporter: Jan Dieckmann
>            Assignee: Robert Scholte
>         Attachments: AbstractIdeSupportMojo.java, MECLIPSE-284.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to