[jbosstools-issues] [JBoss JIRA] (JBDS-2801) Investigate use of GWT/GPE 3.4 in JBT/JBDS Central

[Martin Malina (JIRA)]

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

Martin Malina commented on JBDS-2801:
-------------------------------------

Hey [~nickboldt], "6. Help > Check for updates" didn't do anything because [1] does not contain google plugins. I added the central TP [2] and then I was able to upgrade to the new version of gwt plugins.
Other than that, it works as expected - I ended up with the new version.

[1] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_71/all/repo/
[2] http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.31.0.CR1-SNAPSHOT/REPO/

[~mmurray], can you find a place to document this special process that is required to update from the previous version of the google plugins to the new version? This will affect users that have previously installed Google Plugins via JBoss Central in JBDS 7.0.x and will now wish to update to GWT/GPE 3.4 - as Nick showed, simple Help -> Check for updates will not work for those users - it will not update the Google Plugin for Eclipse properly. This all is assuming we support upgrade from JBDS 7.0.x to 7.1.0 - I believe that is true.
                
> Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
> --------------------------------------------------
>
>                 Key: JBDS-2801
>                 URL: https://issues.jboss.org/browse/JBDS-2801
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: 3rd-party-certification, 3rd-party-dependencies, central
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>              Labels: new_and_noteworthy
>             Fix For: 7.1.0.CR1
>
>         Attachments: JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE_installed_manual_install_of_GPEe43_throws_remediation.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE_installed_view.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1_remdiation_option_1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1_remdiation_option_2.png, JBDS2801_install_JBDS_Beta1_b441_installed.png, JBDS2801_install_JBT_CR1.png, JBDS2801_install_JBT_CR1_installed.png
>
>
> New 3.4.2 mirrors:
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v201310081840-rel-r42/
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v201310081834-rel-r43/
> Note that at least one IU had been renamed:
> OLD: 
> * com.google.gdt.eclipse.suite.e42.feature_3.4.2.v201310081840-rel-r42.jar
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081840-rel-r42.jar
> NEW: 
> * com.google.gdt.eclipse.suite.e43.feature_3.4.2.v201310081834-rel-r43.jar (now e43)
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081834-rel-r43.jar (still e42)
> If we decide to move to e43, we will have to rebuild jbosstools-central due to this requirement:
> {code:title=https://github.com/jbosstools/jbosstools-central/blob/jbosstools-4.1.x/maven/features/org.jboss.tools.maven.gwt.feature/feature.xml#L24}
>       <import feature="com.google.gdt.eclipse.suite.e42.feature" version="3.0.1" match="greaterOrEqual"/>
> {code}

--
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