[ http://jira.codehaus.org/browse/MPECLIPSE-105?page=all ]
fabrizio giustina updated MPECLIPSE-105:
----------------------------------------
Fix Version: (was: 1.9)
> Ability to add projects of local group to build path
> ----------------------------------------------------
>
> Key: MPECLIPSE-105
> URL: http://jira.codehaus.org/browse/MPECLIPSE-105
> Project: maven-eclipse-plugin
> Type: Improvement
> 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 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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
