[jbosstools-issues] [JBoss JIRA] (JBIDE-13018) Forge: "Link with Editor" does not work correctly for multi-module maven projects

Lukáš Fryč (JIRA) jira-events at lists.jboss.org
Thu Nov 8 10:09:17 EST 2012


     [ https://issues.jboss.org/browse/JBIDE-13018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lukáš Fryč updated JBIDE-13018:
-------------------------------

    Attachment: forge-link-to-editor.png

    
> Forge: "Link with Editor" does not work correctly for multi-module maven projects
> ---------------------------------------------------------------------------------
>
>                 Key: JBIDE-13018
>                 URL: https://issues.jboss.org/browse/JBIDE-13018
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: forge
>    Affects Versions: 3.3.1
>            Reporter: Lukáš Fryč
>            Assignee: Koen Aers
>         Attachments: forge-link-to-editor.png
>
>
> When I turn on "Link with Editor" in Forge console,
> and start to switch between Java files, new editor is opened.
> See attached screenshot.
> Note that the editors differs in the file path opened for {{TestFocusManager.java}}:
> * first: {{ui/src/test/java/...}}
> * second: {{components/misc/ui/src/test/java/...}}
> ----
> It's because detected files use wrong project as base.
> There are several projects in a structure:
> {code}
> components/pom.xml
> components/misc/pom.xml
> components/misc/ui/pom.xml
> {code}
> The Forge console detects right one (the most nested): {{[richfaces-ui-misc-ui] TestFocusManager.java $ }}
> But "Link to Editor" uses {{components/}} as a base.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the jbosstools-issues mailing list