[jira] Commented: (MECLIPSE-495) excludes should support *

["Will Horn (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MECLIPSE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151546#action_151546 ] 

Will Horn commented on MECLIPSE-495:
------------------------------------

After looking through the code, I think a great solution would be to externalize the "resolveDependencies" flag.  Now subclass mojos are allowed to set this but I think there is a valid use case for the end user.  For example, I could then use this:

      <plugin>
        <artifactId>maven-eclipse-plugin</artifactId>
        <configuration>
          <pde>true</pde>
          <resolveDependencies>false</resolveDependencies>
        </configuration>
      </plugin>


> excludes should support *
> -------------------------
>
>                 Key: MECLIPSE-495
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-495
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>    Affects Versions: 2.5.1
>         Environment: Windows Vista, Maven 2.0.9
>            Reporter: Will Horn
>
> I am using eclipse:eclipse (with pde=true) and the manifest is handwritten to find OSGi bundles for its dependencies in the Eclipse target platform (the org.eclipse.pde.core.requiredPlugins classpath container).  
> As a result, I don't want the eclipse:eclipse goal to generate classpath (and Bundle-Classpath) entries for all of my 30 or so dependencies.  Currently I can work around it by adding a huge list of excludes, but I really just want to exclude everything.
> I think this is related to http://jira.codehaus.org/browse/MECLIPSE-79

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