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

Martin Malina (JIRA) jira-events at lists.jboss.org
Fri Nov 29 04:19:06 EST 2013


     [ https://issues.jboss.org/browse/JBDS-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Malina updated JBDS-2801:
--------------------------------

    Attachment: install-new-gpe-1.png
                install-new-gpe-2.png
                install-new-gpe-3.png
                install-new-gpe-4.png


OK, so I verified the update process and here's what the users will see:
As I pointed out in my previous comments, 3rd party plugins installed via central will not be updated automatically using Help -> Check for updates.
When JBDS 7.1.0 goes live, central will point to the new content, but unfortunately the only indication of a newer version of a feature will be that the feature will be shown in the list even if it has already be installed. Here on the picture I have already the older version of the google plugins installed:
!install-new-gpe-1.png!

When I chose to install the new GPE and JBoss Maven GWT Configurator, I saw this:
!install-new-gpe-2.png!

I then needed to click the second option - Update my installation to be compatible with the items being installed:
!install-new-gpe-3.png!
Note that this remediation is only needed here because of the GPE plugin name change from com.google.gdt.eclipse.suite.e42.feature to com.google.gdt.eclipse.suite.e43.feature. With other features it should just be a smooth update.

After finishing the install and restarting JBDS and selecting Help -> Install new software -> already installed I saw this:
!install-new-gpe-4.png!

The only blank I need to fill is whether the new central content will be visible once 7.1 goes GA or after the user updates to the 7.1 product (using Help -> Check for updates). I assume the former is true. The latter would only be true if we used a new discovery url for central and the update to 7.1 would update that. [~nickboldt] can you confirm?

All in all, the conclusion is that unfortunately at present we don't have a smooth way for users to update their features installed via JBoss Central (no Help -> Check for update).
                
> 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: install-new-gpe-1.png, install-new-gpe-2.png, install-new-gpe-3.png, install-new-gpe-4.png, 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


More information about the jbosstools-issues mailing list