[ https://issues.jboss.org/browse/JBIDE-10301?page=com.atlassian.jira.plugi... ] SBS JIRA Integration updated JBIDE-10301: ----------------------------------------- Forum Reference: http://community.jboss.org/message/639190#639190 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10301?page=com.atlassian.jira.plugi... ] Vitali Yemialyanchyk commented on JBIDE-10301: ---------------------------------------------- this functionality works correctly in latest whole JBDevStudio M4... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10301?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-10301: ----------------------------------------- I have used the project suggested in JBIDE-10173 to reproduce the issue. All the steps from JBIDE-10173 were done exactly as described in Steps to Reproduce except the step 4: When I just do the Ctrl-LetfClick no TLD-file was found for <stopka:css /> tag - this is because actually there are 3 open-ons registered for this tag and the first (the WTP one) cannot find the appropriate TLD-file. So, I've used JBoss Tools open-on due to open the TLD-file as follows: Step #4: Move mouse over <stopka:css /> tag name while Ctrl-key is pressed. The listof possible open-ons will be displayed for the tag <stopka:css />. Select "Open 'stopka-ui-base-1.0.1.jar :stopka.tld : css'" open-on (which was second for me) to open the stopka.tld file. After the stopka.tld was opened in JBoss Tools Tag Library Editor, other file (test.jspx) still was selected in Package Explorer. When I pressed 'Link with Editor' button, the appropriate file was selected in Package Explorer. The changing the active editor/selecting the other files in Package explorer didn't brake this functionality: when the JBoss Tools Tag Librari Editor is active it could be linked to according stopka.tld file in Package Explorer by pressing 'Link With Editor' button. So, the issue is not reproducible for me. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10301?page=com.atlassian.jira.plugi... ] Victor Rubezhny edited comment on JBIDE-10301 at 12/6/11 12:59 PM: ------------------------------------------------------------------- I have used the project suggested in JBIDE-10173 to reproduce the issue. All the steps from JBIDE-10173 were done exactly as described in Steps to Reproduce except the step 4: When I just do the Ctrl-LetfClick no TLD-file was found for <stopka:css /> tag - this is because actually there are 3 open-ons registered for this tag and the first (the WTP one) cannot find the appropriate TLD-file. So, I've used JBoss Tools open-on due to open the TLD-file as follows: Step #4: Move mouse over <stopka:css /> tag name while Ctrl-key is pressed. The list of possible open-ons will be displayed for the tag <stopka:css />. Select "Open 'stopka-ui-base-1.0.1.jar :stopka.tld : css'" open-on (which was second for me) to open the stopka.tld file. After the stopka.tld was opened in JBoss Tools Tag Library Editor, other file (test.jspx) still was selected in Package Explorer. When I pressed 'Link with Editor' button, the appropriate file was selected in Package Explorer. The changing the active editor/selecting the other files in Package explorer didn't brake this functionality: when the JBoss Tools Tag Library Editor is active it could be linked to according stopka.tld file in Package Explorer by pressing 'Link With Editor' button. So, the issue is not reproducible for me. was (Author: vrubezhny): I have used the project suggested in JBIDE-10173 to reproduce the issue. All the steps from JBIDE-10173 were done exactly as described in Steps to Reproduce except the step 4: When I just do the Ctrl-LetfClick no TLD-file was found for <stopka:css /> tag - this is because actually there are 3 open-ons registered for this tag and the first (the WTP one) cannot find the appropriate TLD-file. So, I've used JBoss Tools open-on due to open the TLD-file as follows: Step #4: Move mouse over <stopka:css /> tag name while Ctrl-key is pressed. The listof possible open-ons will be displayed for the tag <stopka:css />. Select "Open 'stopka-ui-base-1.0.1.jar :stopka.tld : css'" open-on (which was second for me) to open the stopka.tld file. After the stopka.tld was opened in JBoss Tools Tag Library Editor, other file (test.jspx) still was selected in Package Explorer. When I pressed 'Link with Editor' button, the appropriate file was selected in Package Explorer. The changing the active editor/selecting the other files in Package explorer didn't brake this functionality: when the JBoss Tools Tag Library Editor is active it could be linked to according stopka.tld file in Package Explorer by pressing 'Link With Editor' button. So, the issue is not reproducible for me. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10301?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-10301. ------------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira