maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "fabrizio giustina (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MECLIPSE-92) Allow .classpath generation for plugin-development support
Date Wed, 05 Apr 2006 07:54:49 GMT
    [ http://jira.codehaus.org/browse/MECLIPSE-92?page=comments#action_62835 ] 

fabrizio giustina commented on MECLIPSE-92:
-------------------------------------------

>From MECLIPSE-93

Plugin bundles reference other plugins and their references to each other are configured via
the requiredPlugins classpath container. By including src entries to the referenced "plugins"
this results in an error.

Along with not adding src entries for referenced "plugin-projects" project references should
be removed as well in the .project file.

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

>     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


Mime
View raw message