March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-303) Devs to review BrowserSim chapter for JBDS 7.0

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-303?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-303: ------------------------------------- Description: Please review the content of the BrowserSim chapter from a technical viewpoint: 1) Are features correctly documented? 2) Are there any features that are missing? Available at: https://docs.jboss.org/author/display/JBIDE/BrowserSim was: Please review the content of the BrowserSim chapter from a technical viewpoint: 1) Are features correctly documented? 2) Are there any features that are missing? > Devs to review BrowserSim chapter for JBDS 7.0 > ---------------------------------------------- > > Key: TOOLSDOC-303 > URL: https://issues.jboss.org/browse/TOOLSDOC-303 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: UserGuide - BrowserSim > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > > Please review the content of the BrowserSim chapter from a technical viewpoint: > 1) Are features correctly documented? > 2) Are there any features that are missing? > Available at: https://docs.jboss.org/author/display/JBIDE/BrowserSim -- 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] (TOOLSDOC-303) Devs to review BrowserSim chapter for JBDS 7.0

by Michelle Murray (JIRA)

Michelle Murray created TOOLSDOC-303: ---------------------------------------- Summary: Devs to review BrowserSim chapter for JBDS 7.0 Key: TOOLSDOC-303 URL: https://issues.jboss.org/browse/TOOLSDOC-303 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: UserGuide - BrowserSim Affects Versions: 4.1.0 Reporter: Michelle Murray Assignee: Michelle Murray Please review the content of the BrowserSim chapter from a technical viewpoint: 1) Are features correctly documented? 2) Are there any features that are missing? -- 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-13870) Can't re-add BrowserSim toolbar to perspective

by Michelle Murray (JIRA)

Michelle Murray created JBIDE-13870: --------------------------------------- Summary: Can't re-add BrowserSim toolbar to perspective Key: JBIDE-13870 URL: https://issues.jboss.org/browse/JBIDE-13870 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 4.0.0.Final Environment: Fedora 17, JBDS 6 standalone Reporter: Michelle Murray Assignee: Yahor Radtsevich I removed the BrowserSim tool bar from the JBoss perspective and then tried to re-add it. But the check box was already selected, indicating it was already enabled, yet the toolbar still wasn't visible. I went back to JBDS 5 to see if it was a problem there to but it doesn't appear to be. This problem is not restricted to the JBoss perspective. -- 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13837?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13837: ------------------------------------ [~scabanovich], [~akazakov]: why are there 2 PRs for JST, but only one for JavaEE? https://github.com/jbosstools/jbosstools-jst/pull/87 JST 4.0.x https://github.com/jbosstools/jbosstools-jst/pull/85 JST master https://github.com/jbosstools/jbosstools-javaee/pull/66 JavaEE master Is there another PR for JavaEE to be applied for the 4.0.x branch? (cc: [~maxandersen] [~ldimaggio]) > 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.2.Final, 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-13821) CI runs tests against minimum instead of maximum

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13821?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13821: ------------------------------------ [~maxandersen]: if you're happy here, please close this JIRA. > CI runs tests against minimum instead of maximum > ------------------------------------------------ > > Key: JBIDE-13821 > URL: https://issues.jboss.org/browse/JBIDE-13821 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.0.x, 4.1.0.Alpha2 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > > As Maven executions set a value for the TARGET_PLATFORM_VERSION value, this property is not overriden by the maximum profile. > Maven order to set properties is > # look a -D... to set property, if not found > # look at active profiles to set property, if not found > # look at default value of property to set it > This makes that in mvn execution for tests, the TARGET_PLATFORM_VERSION is set to minimal is CI jobs, whereas with using the -Pmaximun profile, we expect maximum. > This is a critical issue since it caused hours of confusions to debug on 4.0.x branch. -- 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13844?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13844: ------------------------------------ If this was fixed before 4.0.1 is released, then please label it respin-b and set the fixVersion to 4.0.1.Final > 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.2.Final, 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-13837) KB Builder does complete scanning of content of every jar file

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13837?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13837: ------------------------------------ If this was fixed before 4.0.1 is released, then please label it respin-b and set the fixVersion to 4.0.1.Final > 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.2.Final, 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-13837) KB Builder does complete scanning of content of every jar file

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13837?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13837: ----------------------------------- Fix Version/s: 4.0.2.Final (was: 4.0.1.Final) > 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.2.Final, 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 Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13844?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13844: ----------------------------------- Fix Version/s: 4.0.2.Final (was: 4.0.1.Final) > 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.2.Final, 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] (JBDS-2503) JBoss EAP developer studio - Issue while adding custom capability

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-2503?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-2503: --------------------------------- Fix Version/s: 6.0.x (was: 6.0.1.GA) > JBoss EAP developer studio - Issue while adding custom capability > ----------------------------------------------------------------- > > Key: JBDS-2503 > URL: https://issues.jboss.org/browse/JBDS-2503 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jsf > Affects Versions: 6.0.0.GA > Environment: Windows > Reporter: Chandrashekhar Tupe > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 6.0.x, 7.0.0.Alpha2 > > Attachments: logfile.txt > > > I am evaluating JBoss EAP and developer studio. Created an enterprise application and wanted to add richface capability to the web app. > Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid". > This happened to me twice and I had to create a new workspace and reconfigure everything from scratch. -- 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