March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2504) JBDS 6.0.1 central software updates contain Juno SR1 fix

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2504?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2504: ---------------------------------- See discussion here: https://issues.jboss.org/browse/JBIDE-13335?focusedCommentId=12760599&pag... and feel free to verify I'm not crazy w/ new JBDS 6.0.1 respin build #360 (which *actually* includes SR2 bits, as fixed in JBDS-2505) :D > JBDS 6.0.1 central software updates contain Juno SR1 fix > -------------------------------------------------------- > > Key: JBDS-2504 > URL: https://issues.jboss.org/browse/JBDS-2504 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build, central > Affects Versions: 6.0.1.GA > Environment: JBDS 6.0.1.CR1a B354 > -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/6.0.1.CR1a.core/devstudio-directory.xml > Reporter: Martin Malina > Assignee: Nick Boldt > Labels: respin-b > Fix For: 6.0.1.GA > > > Today I noticed that in the Software Updates tab of Central in JBDS 6.0.1 I can see the Juno SR1 performance fix. > Since JBDS 6.0.1 is based on SR2, this has nothing to do there. > Actually I was able to install this update because this build of JBDS is in fact based on Juno SR0 - I created JBDS-2505 for that. > Anyway, it should be removed from central for 6.0.1. -- 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-2504) JBDS 6.0.1 central software updates contain Juno SR1 fix

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2504?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2504. ---------------------------- Resolution: Done > JBDS 6.0.1 central software updates contain Juno SR1 fix > -------------------------------------------------------- > > Key: JBDS-2504 > URL: https://issues.jboss.org/browse/JBDS-2504 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build, central > Affects Versions: 6.0.1.GA > Environment: JBDS 6.0.1.CR1a B354 > -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/6.0.1.CR1a.core/devstudio-directory.xml > Reporter: Martin Malina > Assignee: Nick Boldt > Labels: respin-b > Fix For: 6.0.1.GA > > > Today I noticed that in the Software Updates tab of Central in JBDS 6.0.1 I can see the Juno SR1 performance fix. > Since JBDS 6.0.1 is based on SR2, this has nothing to do there. > Actually I was able to install this update because this build of JBDS is in fact based on Juno SR0 - I created JBDS-2505 for that. > Anyway, it should be removed from central for 6.0.1. -- 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-2504) JBDS 6.0.1 central software updates contain Juno SR1 fix

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2504?page=com.atlassian.jira.plugin.... ] Nick Boldt reopened JBDS-2504: ------------------------------ > JBDS 6.0.1 central software updates contain Juno SR1 fix > -------------------------------------------------------- > > Key: JBDS-2504 > URL: https://issues.jboss.org/browse/JBDS-2504 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build, central > Affects Versions: 6.0.1.GA > Environment: JBDS 6.0.1.CR1a B354 > -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/6.0.1.CR1a.core/devstudio-directory.xml > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 6.0.1.GA > > > Today I noticed that in the Software Updates tab of Central in JBDS 6.0.1 I can see the Juno SR1 performance fix. > Since JBDS 6.0.1 is based on SR2, this has nothing to do there. > Actually I was able to install this update because this build of JBDS is in fact based on Juno SR0 - I created JBDS-2505 for that. > Anyway, it should be removed from central for 6.0.1. -- 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-2504) JBDS 6.0.1 central software updates contain Juno SR1 fix

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2504?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2504: ----------------------------- Labels: respin-b (was: ) > JBDS 6.0.1 central software updates contain Juno SR1 fix > -------------------------------------------------------- > > Key: JBDS-2504 > URL: https://issues.jboss.org/browse/JBDS-2504 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build, central > Affects Versions: 6.0.1.GA > Environment: JBDS 6.0.1.CR1a B354 > -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/6.0.1.CR1a.core/devstudio-directory.xml > Reporter: Martin Malina > Assignee: Nick Boldt > Labels: respin-b > Fix For: 6.0.1.GA > > > Today I noticed that in the Software Updates tab of Central in JBDS 6.0.1 I can see the Juno SR1 performance fix. > Since JBDS 6.0.1 is based on SR2, this has nothing to do there. > Actually I was able to install this update because this build of JBDS is in fact based on Juno SR0 - I created JBDS-2505 for that. > Anyway, it should be removed from central for 6.0.1. -- 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-2505) JBDS 6.0.1 is based on Juno SR0 instead of SR2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2505?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2505: ----------------------------- Labels: respin-b (was: ) > JBDS 6.0.1 is based on Juno SR0 instead of SR2 > ---------------------------------------------- > > Key: JBDS-2505 > URL: https://issues.jboss.org/browse/JBDS-2505 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 6.0.1.GA > Environment: JBDS 6.0.1.CR1a B354 > Reporter: Martin Malina > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-b > Fix For: 6.0.1.GA > > > JBDS 6.0.1.CR1a B354 is based on Eclipse Juno SR0, but should be Juno SR2. > I know about the recent issue where TP wasn't updated to 4.22.2, so I would expect something 4.22.1 (still Juno SR2). But in fact it is SR0. > My assumption is that while JBDS BYOE can be installed on the minimal version of Eclipse, the JBDS installer should contain the maximum TP. I hope I'm not wrong here. > Now I also checked the previous build - JBDS 6.0.1.CR1 B338 and that is based on Eclipse Juno 4.2.1. -- 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 updated JBIDE-13837: ------------------------------- Labels: respin-b (was: ) > 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 > Labels: respin-b > 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13837?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13837: ------------------------------- Fix Version/s: 4.0.1.Final (was: 4.0.2.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 > Labels: respin-b > Fix For: 4.0.1.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] (JBDS-2504) JBDS 6.0.1 central software updates contain Juno SR1 fix

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-2504?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-2504: ------------------------------------- I'm surprised that the fix can be installed even on top of SR2. But if you say it doesn't hurt then I don't object. > JBDS 6.0.1 central software updates contain Juno SR1 fix > -------------------------------------------------------- > > Key: JBDS-2504 > URL: https://issues.jboss.org/browse/JBDS-2504 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build, central > Affects Versions: 6.0.1.GA > Environment: JBDS 6.0.1.CR1a B354 > -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/6.0.1.CR1a.core/devstudio-directory.xml > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 6.0.1.GA > > > Today I noticed that in the Software Updates tab of Central in JBDS 6.0.1 I can see the Juno SR1 performance fix. > Since JBDS 6.0.1 is based on SR2, this has nothing to do there. > Actually I was able to install this update because this build of JBDS is in fact based on Juno SR0 - I created JBDS-2505 for that. > Anyway, it should be removed from central for 6.0.1. -- 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 updated JBIDE-13844: ------------------------------- Labels: respin-b (was: ) > 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 > Labels: respin-b > 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-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 updated JBIDE-13844: ------------------------------- Fix Version/s: 4.0.1.Final (was: 4.0.2.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 > Labels: respin-b > Fix For: 4.0.1.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

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