[ http://jira.codehaus.org/browse/MECLIPSE-93?page=all ] Sachin Patel reopened MECLIPSE-93: ----------------------------------
Actually, sorry will need to reopen this. While the statement is true for Java Projects, for plugin development it is not. 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. I'm beginning to think it would be useful to provide a flag in the configuration to better handle the "plugin-development" case. > Incorrect src entry being added in .classpath for referenced projects > --------------------------------------------------------------------- > > Key: MECLIPSE-93 > URL: http://jira.codehaus.org/browse/MECLIPSE-93 > Project: Maven 2.x Eclipse Plugin > Type: Bug > Versions: 2.1 > Reporter: Sachin Patel > Assignee: fabrizio giustina > Fix For: 2.1 > > > The generated .classpath contains src entries for each project referenced in > the .project. This is incorrect, these entries should be removed. For > example.. > Consider Project A and Project B. If A depends on B, A's .project file > contains a reference to Project B which is correct, but its classpath > contains a src entry to the root of B, which should not be there. > There seem to be additional src entries as well, which seems to mess things > up (at least for eclipse-plugin development) which I'll dig into and open > jiras on as well. -- 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
