[ https://issues.jboss.org/browse/JBDS-1935?page=com.atlassian.jira.plugin.... ] Snjezana Peco commented on JBDS-1935: ------------------------------------- I can't reproduce the issue on Windows 32-bit and Linux 32-bit. What OS are you using? What happens when you close the JBoss Central editor and open it again? -- 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/JBDS-1935?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-1935: ----------------------------- Attachment: resizing-fine-after-restart.png -- 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/JBDS-1935?page=com.atlassian.jira.plugin.... ] Snjezana Peco commented on JBDS-1935: ------------------------------------- Nick, What OS are you using? -- 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/JBDS-1935?page=com.atlassian.jira.plugin.... ] Snjezana Peco commented on JBDS-1935: ------------------------------------- I can't reproduce the issue on Fedora 15 X86-64 Gnome. I have tested it with the same kernel and java as you used. Suppose that there is a problem with GTK libraries within Fedora KDE. Can you reproduce the issue every time: - when restarting JBDS in a new workspace - when reinstalling JBDS from scratch When you reproduce the issue, does closing/opening the JBoss Central editor fix the issue? -- 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/JBDS-1935?page=com.atlassian.jira.plugin.... ] Nick Boldt reopened JBDS-1935: ------------------------------ Was able to reproduce this: 1. unpack clean eclipse-jee-indigo-SR1-linux-gtk-x86_64.tar.gz 2. install JBoss Central features from JBT nightly site 3. install JBDS (all) from nightly product site 4. on restart, Central is mangled. Closing/restarting Central view makes it work fine again. -- 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/JBDS-1935?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-1935 at 12/1/11 10:40 PM: ------------------------------------------------------------ Was able to reproduce this: 1. unpack clean eclipse-jee-indigo-SR1-linux-gtk-x86_64.tar.gz 2. install 2 JBoss Central features from JBT nightly site (http://download.jboss.org/jbosstools/updates/nightly/core/trunk/). Restart. 3. on restart, Central is mangled. Closing/restarting Central view makes it work fine again. Resulting install config: Eclipse IDE for Java EE Developers 1.4.1.20110909-1818 epp.package.jee JBoss Central 1.0.0.v20111201-2314-H57-M5 org.jboss.tools.central.feature.feature.group JBoss Central Community 1.0.0.v20111201-2314-H57-M5 org.jboss.tools.community.central.feature.feature.group !jboss-central-squished-on-restart-again.png! -- 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/JBDS-1935?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-1935: ------------------------------------------- is this fixed/out of date or ? -- 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/JBDS-1935?page=com.atlassian.jira.plugin.... ] Snjezana Peco commented on JBDS-1935: ------------------------------------- I tried to reproduce the issue on Windows XP 32-bit, Linux 32-bit and Linux 64-bit (Fedora 15), but didn't succeed. -- 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/JBDS-1935?page=com.atlassian.jira.plugin.... ] Snjezana Peco commented on JBDS-1935: ------------------------------------- export GDK_NATIVE_WINDOWS=true could be the cause of the issue. Could you try to reproduce it without this line? -- 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/JBDS-1935?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-1935 at 12/6/11 8:07 PM: ----------------------------------------------------------- Further testing indicates that it's the Welcome screen that's to blame. 1. Unpack JEE bundle, start. DO NOT CLOSE the Welcome screen. 2. Help > Install > Add 3.3.indigo nightly update site: http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/ 3. Install ONLY the two Central features (which will bring in the Community Examples feature); while installing tell Eclipse to always run this stuff in the background. Restart when prompted -- KEEPING THE WELCOME SCREEN VISIBLE. 4. On restart, minimize (or close) the Welcome screen: JBoss Central is incorrectly sized. If closed and relaunched from the toolbar button, it's fine. 5. Close Central, remaximize (or open) the Welcome screen. Restart Eclipse from File > Restart. 6. On restart, minimize (or close) the Welcome screen: JBoss Central is incorrectly sized. If closed and relaunched from the toolbar button, it's fine. 7. Close the Welcome screen, close Central, and restart Eclipse. Now (since I still have "Show on Startup" checked) Central re-appears and properly sized on startup. I've tried launching w/ and w/o the `export GDK_NATIVE_WINDOWS=true` line, and even dropping memory settings to launch simply like this: `./eclipse/eclipse -data /home/nboldt/eclipse/workspace-clean37 -consolelog -console` Doesn't seem to matter what I do -- if the Welcome screen is maximized on startup, Central will be corrupted. Even the smaller Welcome screen is fine -- the effect is 100% reproduceable ONLY when the Welcome screen is maximized on startup (even if Central was fine underneath it, it'll be corrupted on restart). was (Author: nickboldt): Further testing indicates that it's the Welcome screen that's to blame. 1. Unpack JEE bundle, start. DO NOT CLOSE the Welcome screen. 2. Help > Install > Add 3.3.indigo nightly update site: http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/ 3. Install ONLY the two Central features (which will bring in the Community Examples feature); while installing tell Eclipse to always run this stuff in the background. Restart when prompted -- KEEPING THE WELCOME SCREEN VISIBLE. 4. On restart, minimize (or close) the Welcome screen: JBoss Central is incorrectly sized. If closed and relaunched from the toolbar button, it's fine. 5. Close Central, remaximize (or open) the Welcome screen. Restart Eclipse from File > Restart. 6. On restart, minimize (or close) the Welcome screen: JBoss Central is incorrectly sized. If closed and relaunched from the toolbar button, it's fine. 7. Close the Welcome screen, close Central, and restart Eclipse. Now (since I still have "Show on Startup" checked) Central re-appears and properly sized on startup. -- 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/JBDS-1935?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-1935: ---------------------------------- Can reproduce this effect in JBDS 5.0.0.Beta1 too. If Welcome screen is maximized on start of Eclipse, JBoss Central will be corrupted, unresizable, and squeezed into a tiny part of the editor space. And of course it's fine if I close it and relaunch it from the toolbar button. -- 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/JBDS-1935?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-1935: ---------------------------------- 1. install JBDS 5.0.0.M5 from jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201112080344M-H52-M5.jar {code} $ java -jar *-product-linux-gtk-x86_64-5.0.0.v201112080344M-H52-M5* {code} 2. start up from commandline: {code} $ cd /home/nboldt/jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201112080344M-H52-M5 $ ./jbdevstudio {code} 3. If I minimize or close [x] the Welcome screen, Central is mangled as reported above. But if I click the 'Get started with JBoss Central' button on the Welcome screen, Central is fine. In fact, while Central is mangled, if you re-open the Welcome screen and click the 'Get started with JBoss Central' button, Central becomes properly sized (unmangled). -- 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/JBDS-1935?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-1935: ---------------------------------- Still waiting for a patch ... I assumed you'd attach it here. Or should I test from https://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/org.jboss.too... ? -- 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/JBDS-1935?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-1935: ---------------------------------- Cannot install from your site into JBDS 5.0.0.M5 v20111207-2332-H47-M5 because the timestamp is OLDER than the latest version. Installed: 1.0.0.v20111207-1112-H12-M5 Your version: 1.0.0.201112082045 (note that in p2 land, "v" is newer than "2") Could you just use the maven build script I provided in the central/site/ folder? That will build an update site conforming to the versioning rules used in JBT/JBDS for features. Or, better yet, attach a patch so I can test it here and commit it w/o us having to both be online concurrently. -- 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/JBDS-1935?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-1935 at 12/8/11 10:07 PM: ------------------------------------------------------------ Cannot install from your site into JBDS 5.0.0.M5 v20111207-2332-H47-M5 because the timestamp is OLDER than the latest version. Installed: 1.0.0.v20111207-1112-H12-M5 Your version: 1.0.0.201112082045 (note that in p2 land, "v" is newer than "2") Could you just use the maven build script I provided in the central/site/ folder? That will build an update site conforming to the versioning rules used in JBT/JBDS for features. Or, better yet, attach a patch so I can test it here and commit it w/o us having to both be online concurrently. Other reason for a patch is that we're in code freeze so in theory all late-breaking changes should be done w/ accompanying patch for verification. (That doesn't happen in 100% of cases but that's the goal.) Am now installing from your site into a clean Eclipse 3.7.1 JEE on linux 64 to test. was (Author: nickboldt): Cannot install from your site into JBDS 5.0.0.M5 v20111207-2332-H47-M5 because the timestamp is OLDER than the latest version. Installed: 1.0.0.v20111207-1112-H12-M5 Your version: 1.0.0.201112082045 (note that in p2 land, "v" is newer than "2") Could you just use the maven build script I provided in the central/site/ folder? That will build an update site conforming to the versioning rules used in JBT/JBDS for features. Or, better yet, attach a patch so I can test it here and commit it w/o us having to both be online concurrently. Other reason for a patch is that we're in code freeze so in theory all late-breaking changes should be done w/ accompanying patch for verification. (That doesn't happen in 100% of cases but that's the goal. Am now installing from your site into a clean Eclipse 3.7.1 JEE on linux 64 to test. -- 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/JBDS-1935?page=com.atlassian.jira.plugin.... ] Snjezana Peco resolved JBDS-1935. --------------------------------- Resolution: Done Committed to the trunk and jbosstools-3.3.0.M5 branch. -- 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