You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Will Horn (JIRA)" <ji...@codehaus.org> on 2008/10/24 03:20:19 UTC

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

     [ http://jira.codehaus.org/browse/MECLIPSE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Will Horn updated MECLIPSE-495:
-------------------------------

    Attachment: MECLIPSE-495.patch

patch that makes resolveDependencies a parameter

> 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
>         Attachments: MECLIPSE-495.patch
>
>
> 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