You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org> on 2006/08/01 03:48:31 UTC
[jira] Closed: (MNGECLIPSE-170) Attach source code of other Eclipse
project that the project depends on
[ http://jira.codehaus.org/browse/MNGECLIPSE-170?page=all ]
Eugene Kuleshov closed MNGECLIPSE-170.
--------------------------------------
Resolution: Duplicate
> Attach source code of other Eclipse project that the project depends on
> -----------------------------------------------------------------------
>
> Key: MNGECLIPSE-170
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-170
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Improvement
> Affects Versions: 0.0.9
> Environment: Linux, Eclipse 3.1.2, m2eclipse .0.09
> Reporter: Jimisola Laursen
> Assigned To: Eugene Kuleshov
>
> I have projects with dependencies between them and these dependencies are represented in Eclipse correctly.
> When I use F3 ("Open Declaration") in Eclipse on a method/class/etc defined in another project than the current one the source is not found.
> I assume that if I'd have had the source in the repository then it would have been used.
> However, I would like for Eclipse to go to the (fresh) source code in the actual project instead. If I am developing in say project A and B I otherwise have to install source-jars to the repository to get the correct version of A's source code when I hit F3 in project B. That is, attach source code of other Eclipse project that the project depends on.
--
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