March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13856) Test jQuery Mobile Palette Wizards on different platforms

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13856?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-13856: ---------------------------------- Attachment: ubuntu_64_textinput.png ubuntu_64_slider.png ubuntu_64_checkboxes.png ubuntu_64_cjeckbox.png ubuntu_64_radio.png ubuntu_64_toggle.png ubuntu_64_link.png ubuntu_64_button.png ubuntu_64_listview.png ubuntu_64_navbar.png ubuntu_64_footerbar.png ubuntu_64_headerbar.png ubuntu_64_collapsible.png ubuntu_64_grid.png ubuntu_64_dialog.png ubuntu_64_page.png > Test jQuery Mobile Palette Wizards on different platforms > --------------------------------------------------------- > > Key: JBIDE-13856 > URL: https://issues.jboss.org/browse/JBIDE-13856 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Fix For: 4.1.0.Alpha2 > > Attachments: ubuntu_64_button.png, ubuntu_64_checkboxes.png, ubuntu_64_cjeckbox.png, ubuntu_64_collapsible.png, ubuntu_64_dialog.png, ubuntu_64_footerbar.png, ubuntu_64_grid.png, ubuntu_64_headerbar.png, ubuntu_64_link.png, ubuntu_64_listview.png, ubuntu_64_navbar.png, ubuntu_64_page.png, ubuntu_64_radio.png, ubuntu_64_slider.png, ubuntu_64_textinput.png, ubuntu_64_toggle.png > > -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13856) Test jQuery Mobile Palette Wizards on different platforms

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13856?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-13856: ---------------------------------- Fix Version/s: 4.1.0.Alpha2 > Test jQuery Mobile Palette Wizards on different platforms > --------------------------------------------------------- > > Key: JBIDE-13856 > URL: https://issues.jboss.org/browse/JBIDE-13856 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Fix For: 4.1.0.Alpha2 > > -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13856) Test jQuery Mobile Palette Wizards on different platforms

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-13856: ------------------------------------- Summary: Test jQuery Mobile Palette Wizards on different platforms Key: JBIDE-13856 URL: https://issues.jboss.org/browse/JBIDE-13856 Project: Tools (JBoss Tools) Issue Type: Task Components: jsp/jsf/xml/html source editing Reporter: Daniel Azarov Assignee: Daniel Azarov -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13837) KB Builder does complete scanning of content of every jar file

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13837?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-13837: ------------------------------------------ Git Pull Request: https://github.com/jbosstools/jbosstools-jst/pull/85, https://github.com/jbosstools/jbosstools-javaee/pull/66, https://github.com/jbosstools/jbosstools-jst/pull/87 (was: https://github.com/jbosstools/jbosstools-jst/pull/85, https://github.com/jbosstools/jbosstools-javaee/pull/66) > KB Builder does complete scanning of content of every jar file > --------------------------------------------------------------- > > Key: JBIDE-13837 > URL: https://issues.jboss.org/browse/JBIDE-13837 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.0.x, 4.1.0.Alpha2 > > > Memory problem were reported https://community.jboss.org/message/804026#804026 > At present, KB builder scans for facelet taglibs everywhere in jar files, not only in META-INF folder. That results in complete loading of model objects for jar content, which otherwise would remain unloaded. Once loaded, it is not easy to release them, since objects are shared by projects referencing the same jar. > Complete scanning was implemented as fix for https://issues.jboss.org/browse/JBIDE-5764 in February 2010. > JSF implementation jsf-impl-2.0.1.jar contains facelet tag libraries in /com/sun/faces/metadata/taglib. > However, it is recommended that facelet taglib xml files be packaged into META-INF folder. It seems that jsf-impl-2.0.1.jar is a special case. I suggest that we stop doing complete scanning of all jars and do it only for JSF 2 implementation jar. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2502) org.eclipse.jst.server.generic.oc4j plugin has been removed from WTP 3.5.0 M6

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2502?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2502: ----------------------------- Release Notes Text: org.eclipse.jst.server.generic.oc4j removed from JBDS, because it's no longer part of WTP 3.5.0 as of their M6 release. (was: org.eclipse.jst.server.generic.oc4j removed from JBDS.) > org.eclipse.jst.server.generic.oc4j plugin has been removed from WTP 3.5.0 M6 > ----------------------------------------------------------------------------- > > Key: JBDS-2502 > URL: https://issues.jboss.org/browse/JBDS-2502 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 7.0.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Nick Boldt > Fix For: 7.0.0.Alpha2 > > Attachments: oc4j.patch > > > The devstudio.product_trunk build (http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_tru...) fails because the org.eclipse.jst.server.generic.oc4j plugin has been removed from WTP 3.5.0 M6. > Attached is a patch. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2502) org.eclipse.jst.server.generic.oc4j plugin has been removed from WTP 3.5.0 M6

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2502?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-2502. ------------------------------ Release Notes Docs Status: Not Yet Documented Release Notes Text: org.eclipse.jst.server.generic.oc4j removed from JBDS. Fix Version/s: 7.0.0.Alpha2 Resolution: Done Patch applied - thanks! Job respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_tr... >=3377 I won't ask for unit test plugins for this change. :) > org.eclipse.jst.server.generic.oc4j plugin has been removed from WTP 3.5.0 M6 > ----------------------------------------------------------------------------- > > Key: JBDS-2502 > URL: https://issues.jboss.org/browse/JBDS-2502 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 7.0.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Nick Boldt > Fix For: 7.0.0.Alpha2 > > Attachments: oc4j.patch > > > The devstudio.product_trunk build (http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_tru...) fails because the org.eclipse.jst.server.generic.oc4j plugin has been removed from WTP 3.5.0 M6. > Attached is a patch. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13844) JarAccess should ignore .class entries in jar files

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13844?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-13844: ------------------------------------------ Fix Version/s: 4.0.x > JarAccess should ignore .class entries in jar files > --------------------------------------------------- > > Key: JBIDE-13844 > URL: https://issues.jboss.org/browse/JBIDE-13844 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.0.x, 4.1.0.Alpha2 > > > Memory problem were reported https://community.jboss.org/message/804026#804026 > JarAccess is used by internal model to optimize requests to jar files. It builds a map that binds parent folder path to its content. At present, maps include paths for all entries so that in a large workspace with 500-1000 jars memory consumed by these maps may add up to 70Mb. However, for a long time .class entries from JarAccess are not used directly for presentation in ui. Class selector based on it had been replaced by Eclipse's Class selector years ago. Builders in CDI and Seam get classes from JDT model. Open-ons work with JDT elements as well. Hence, if internal model has no more data on .class entries, it should not affect anything, while the profit is significant - memory consumed by maps in JarAccess may drop 5 to 10 times. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13739) CDI Support cannot be disabled if CDI Maven Configurator is installed and enabled

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13739?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-13739: ------------------------------------- The maven CDI configurator automatically enables CDI support if CDI dependencies are detected in the classpath. I see we can improve things a bit : - currently any change on the project would trigger the CDI configurator to run. That includes changing the CDI support in the project properties. We only want the configurator to be invoked manually (maven > update project), or if the project dependencies changed (a cdi dependency was added) - if the CDI nature *AND* the CDI Facet is installed, configuration is skipped. We can choose to skip if one *OR* the other requirement is met. That way, CDI EJB or Web faceted projects can manually disable CDI support. This leaves one corner case : A non faceted project with CDI dependencies. CDI support would be re-enabled after each Maven > Project Update action. How do you think we could handle that use case? > CDI Support cannot be disabled if CDI Maven Configurator is installed and enabled > --------------------------------------------------------------------------------- > > Key: JBIDE-13739 > URL: https://issues.jboss.org/browse/JBIDE-13739 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: CDI, maven > Affects Versions: 4.0.1.Final > Reporter: Denis Golovin > Assignee: Fred Bricon > -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13837) KB Builder does complete scanning of content of every jar file

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13837?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-13837: ------------------------------------------ Fix Version/s: 4.0.x > KB Builder does complete scanning of content of every jar file > --------------------------------------------------------------- > > Key: JBIDE-13837 > URL: https://issues.jboss.org/browse/JBIDE-13837 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.0.x, 4.1.0.Alpha2 > > > Memory problem were reported https://community.jboss.org/message/804026#804026 > At present, KB builder scans for facelet taglibs everywhere in jar files, not only in META-INF folder. That results in complete loading of model objects for jar content, which otherwise would remain unloaded. Once loaded, it is not easy to release them, since objects are shared by projects referencing the same jar. > Complete scanning was implemented as fix for https://issues.jboss.org/browse/JBIDE-5764 in February 2010. > JSF implementation jsf-impl-2.0.1.jar contains facelet tag libraries in /com/sun/faces/metadata/taglib. > However, it is recommended that facelet taglib xml files be packaged into META-INF folder. It seems that jsf-impl-2.0.1.jar is a special case. I suggest that we stop doing complete scanning of all jars and do it only for JSF 2 implementation jar. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13844) JarAccess should ignore .class entries in jar files

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13844?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-13844: ------------------------------------------ Git Pull Request: https://github.com/jbosstools/jbosstools-base/pull/67, https://github.com/jbosstools/jbosstools-base/pull/68 (was: https://github.com/jbosstools/jbosstools-base/pull/67) > JarAccess should ignore .class entries in jar files > --------------------------------------------------- > > Key: JBIDE-13844 > URL: https://issues.jboss.org/browse/JBIDE-13844 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.1.0.Alpha2 > > > Memory problem were reported https://community.jboss.org/message/804026#804026 > JarAccess is used by internal model to optimize requests to jar files. It builds a map that binds parent folder path to its content. At present, maps include paths for all entries so that in a large workspace with 500-1000 jars memory consumed by these maps may add up to 70Mb. However, for a long time .class entries from JarAccess are not used directly for presentation in ui. Class selector based on it had been replaced by Eclipse's Class selector years ago. Builders in CDI and Seam get classes from JDT model. Open-ons work with JDT elements as well. Hence, if internal model has no more data on .class entries, it should not affect anything, while the profit is significant - memory consumed by maps in JarAccess may drop 5 to 10 times. -- 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

13 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2013