[ http://jira.codehaus.org/browse/MECLIPSE-92?page=comments#action_70004 ] fabrizio giustina commented on MECLIPSE-92: -------------------------------------------
Patch committed with a few modifications (remove dependency from commons-io, only show a warning instead of throwing an exception when a manifest file doesn't exist). I am still working on it, I will have to add proper tests for the OsgiManifestWriter, and I will leave this issue open till the work is complete. You might want to give a try at the snapshot at http://people.apache.org/maven-snapshot-repository/org/apache/maven/plugins/maven-eclipse-plugin/2.3-SNAPSHOT/maven-eclipse-plugin-2.3-20060717.195425-1.jar > Allow .classpath generation for plugin-development support > ---------------------------------------------------------- > > Key: MECLIPSE-92 > URL: http://jira.codehaus.org/browse/MECLIPSE-92 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: PDE support > Affects Versions: 2.1 > Reporter: Sachin Patel > Assigned To: fabrizio giustina > Attachments: pde_patch_1.diff > > > 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
