[ https://jira.jboss.org/jira/browse/JBIDE-2808?page=com.atlassian.jira.plu... ] Denis Golovin updated JBIDE-2808: --------------------------------- Fix Version/s: 3.0.0.cr1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2808?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-2808: --------------------------------------- Priority: Blocker (was: Major) This needs to get fixed; it is very limiting that our xhtml completion only work with whatever we've updated kbase to understand. At a minimum TLD's should be considered together with kbase and not solely kbase. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2808?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-2808: -------------------------------------------- 1) initially adding as part of jsf sounds fine (as long as it works with seam projects too. But this is just an installation issue, right ? the KB builder would not depend on JSF nature or would it ? 2) I were wondering if the JSF support in Eclipse collects some of this info (I assume not though) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2808?page=com.atlassian.jira.plu... ] Alexey Kazakov commented on JBIDE-2808: --------------------------------------- Slava suggests adding new builder and nature. Then we will be able to link the model to this new nature and we will be idependend on JSF/Seam natures. Otherwise it's not clear how where we should link the model if there may be JSF or/and Seam natures. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2808?page=com.atlassian.jira.plu... ] Alexey Kazakov updated JBIDE-2808: ---------------------------------- Fix Version/s: 3.1.0.M3 (was: 3.1.0.M2) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2808?page=com.atlassian.jira.plu... ] Alexey Kazakov updated JBIDE-2808: ---------------------------------- Description: Current KB plugin has some problems, which we have to solve. - KB uses a set of XMLs. One XML for one tag library. If we want to support some new tag library we have to convert it to special XML and add it to KB plugin manually. It would be nice to have some default behavior for unknown TLDs. - It doesn't work with facelets tag libraries. - Our XMLs are quite big. It consumes memory in case some JSP/Facelet pages use a lot of tag libraries. Also parsing big XML is quite slow process. It effects time of first starting JSP/HTML editors. See wiki http://www.jboss.org/community/wiki/NewKBplug-inandCodeAssistinJBossTools... was: Current KB plugin has some problems, which we have to solve. - KB uses a set of XMLs. One XML for one tag library. If we want to support some new tag library we have to convert it to special XML and add it to KB plugin manually. It would be nice to have some default behavior for unknown TLDs. - It doesn't work with facelets tag libraries. - Our XMLs are quite big. It consumes memory in case some JSP/Facelet pages use a lot of tag libraries. Also parsing big XML is quite slow process. It effects time of first starting JSP/HTML editors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira