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

Posted to issues@maven.apache.org by "fabrizio giustina (JIRA)" <ji...@codehaus.org> on 2006/04/05 10:00:53 UTC

[jira] Updated: (MECLIPSE-92) Allow .classpath generation for plugin-development support

     [ http://jira.codehaus.org/browse/MECLIPSE-92?page=all ]

fabrizio giustina updated MECLIPSE-92:
--------------------------------------

    type: Improvement  (was: Bug)

> Allow .classpath generation for plugin-development support
> ----------------------------------------------------------
>
>          Key: MECLIPSE-92
>          URL: http://jira.codehaus.org/browse/MECLIPSE-92
>      Project: Maven 2.x Eclipse Plugin
>         Type: Improvement

>     Versions: 2.1
>     Reporter: Sachin Patel
>      Fix For: 2.2

>
>
> In order to improve eclipse plugin development with maven, the configuration of the eclipse:eclipse goal should allow a flag to be set that that given pom is an eclipse plugin and the .classpath generated should not add .classpath entries for dependencies declared in the POM, since plugins really just reference other plugins in the workspace and or use the "requiredPlugins" classpath container.  At runtime plugins cannot reference external classes/jars so having all the "var" entries isn't necessary and adds clutter.

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