[jbosstools-issues] [JBoss JIRA] (JBDS-1935) if Welcome screen is maximized on startup, JBoss Central can't be resized / doesn't auto-resize to fill editor pane

[Nick Boldt (Issue Comment Edited) (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649499#comment-12649499 ] 

Nick Boldt edited comment on JBDS-1935 at 12/8/11 10:25 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.)

---

1. install fresh Indigo 3.7.1 x86_64 linux JEE bundle, as before.

2. Add http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/ and  https://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/org.jboss.tools.central.update/ sites.

3. Select the patch site, and install the single Central feature.

4. Ensure the Welcome screen is open fullscreen in Eclipse before restarting when prompted after install.

5. SUCCESS! When minimizing or closing Welcome, Central is now fully-sized.

6. If you then update to the version of Central on the 3.3.indigo nightly site, you get the previous corrupted effects. 

CONCLUSION: whatever you did, it worked. Commit it ASAP. Thanks!


                
      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.


                  
> if Welcome screen is maximized on startup, JBoss Central can't be resized / doesn't auto-resize to fill editor pane
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBDS-1935
>                 URL: https://issues.jboss.org/browse/JBDS-1935
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: central
>    Affects Versions: 5.0.0.M5
>            Reporter: Nick Boldt
>            Assignee: Snjezana Peco
>            Priority: Blocker
>             Fix For: 5.0.0.M5
>
>         Attachments: jboss-central-squished-on-restart-again.png, resizing-fine-after-restart.png
>
>
> Can't resize Central view, and view won't expand to fill the available editor space. Kinda ugly.
> Does this require some new com.jboss.jbds.central plugin to allow JBoss Central in JBDS to behave differently than JBoss Central (as part of Tools) ?
> Screenshot (from JBDS 5.0.0.v201111221530N-H834-M5 on linux 64-bit):
> !https://issues.jboss.org/secure/attachment/12349274/central-in-jbds-5.0.0.v201111221530N-H834-M5.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