[
https://jira.codehaus.org/browse/MPECLIPSE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPECLIPSE-105.
------------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> Ability to add projects of local group to build path
> ----------------------------------------------------
>
> Key: MPECLIPSE-105
> URL: https://jira.codehaus.org/browse/MPECLIPSE-105
> Project: Maven 1.x Eclipse Plugin
> Issue Type: Improvement
> Affects Versions: 1.9
> Reporter: Rodion Zhitomirsky
> Attachments: PATCH
>
>
> We are using eclipse and maven for our internal project.
> Our project is splitted up into multiple semi-independent projects (modules).
> So, using repository and maven eclipse plugin we were able to work. However,
> there is still one important feature of Eclipse that is not available anymore
> after we swtiched to maven: sources of different projects got decoupled and
> you can not search, for instance, for references to some class or method.
> This could be only fixed by adding referencing projects' source code from
> other projects.
> So, I decided to write a patch for this.
> The point is: during generation of .classpath plugin behaves as usually, with
> an exception of cases, where groupId is the same as
> maven.eclipse.localgroupid. For this case there will be an additional
> classpathentry with reference to project.
> Hope, my patch explains more then this text (it is a little bit mixed :).
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
