[jbosstools-issues] [JBoss JIRA] (JBIDE-10967) add GWT to Extras site and point Central at our copy instead of live version on code.google.com

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-10967 at 2/23/12 3:08 PM:
-------------------------------------------------------------

Need to respin Central component & JBT/JBDS aggregates in both trunk and 33x/5x branches, then test if GWT stuff can be installed from Central like this:

TO VERIFY, check the Software/Update tab in Central and look at the Google Plugin + Web Toolkit installable:

If described as "Google Plugin for Eclipse (GPE) + Google Web Toolkit SDK (GWT)" we're reading from the trunk site.
If described as "Google Plugin for Eclipse (GPE) 2.5.1 + Google Web Toolkit SDK (GWT) 2.4.0" we're reading from the tip of Beta1 branch
If described as "Google Plugin for Eclipse (GPE) + Google Web Toolkit SDK 2.4.0 (GWT)" we're reading from from previous milestone site (M5).

Waiting for:

https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--central/ >=400
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ >=4191
https://hudson.qa.jboss.com/hudson/job/devstudio-5.0_trunk.updatesite/ >=1687
and
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--central/ >=43
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.aggregate/ >=80
https://hudson.qa.jboss.com/hudson/job/devstudio-5.0_stable_branch.updatesite/ >=67

{color:green}*VERIFIED*{color}
./eclipse/eclipse -clean -showLocation -data /tmp/workspace -consolelog -console -vm /opt/sun-java2-6.0/bin/java -vmargs -Xms128M -Xmx256M -XX:PermSize=128M -XX:MaxPermSize=256M  -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/jbosstools-directory.xml  | tee "/tmp/eclipse.log.`date`.txt"

{color:green}*VERIFIED*{color}
./eclipse/eclipse -clean -showLocation -data /tmp/workspace -consolelog -console -vm /opt/sun-java2-6.0/bin/java -vmargs -Xms128M -Xmx256M -XX:PermSize=128M -XX:MaxPermSize=256M  -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.Beta1a.core/jbosstools-directory.xml  | tee "/tmp/eclipse.log.`date`.txt"

{color:red}*PENDING*{color}
./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.updatesite/extras/devstudio-directory.xml

{color:red}*PENDING*{color}
./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta1.extras/devstudio-directory.xml


                
      was (Author: nickboldt):
    Need to respin Central component & JBT/JBDS aggregates in both trunk and 33x/5x branches, then test if GWT stuff can be installed from Central like this:

TO VERIFY, check the Software/Update tab in Central and look at the Google Plugin + Web Toolkit installable:

If described as "Google Plugin for Eclipse (GPE) + Google Web Toolkit SDK (GWT)" we're reading from the trunk site.
If described as "Google Plugin for Eclipse (GPE) 2.5.1 + Google Web Toolkit SDK (GWT) 2.4.0" we're reading from the tip of Beta1 branch
If described as "Google Plugin for Eclipse (GPE) + Google Web Toolkit SDK 2.4.0 (GWT)" we're reading from from previous milestone site (M5).

{code}

{color:green}*VERIFIED*{color}
./eclipse/eclipse -clean -showLocation -data /tmp/workspace -consolelog -console -vm /opt/sun-java2-6.0/bin/java -vmargs -Xms128M -Xmx256M -XX:PermSize=128M -XX:MaxPermSize=256M  -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/jbosstools-directory.xml  | tee "/tmp/eclipse.log.`date`.txt"

{color:green}*VERIFIED*{color}
./eclipse/eclipse -clean -showLocation -data /tmp/workspace -consolelog -console -vm /opt/sun-java2-6.0/bin/java -vmargs -Xms128M -Xmx256M -XX:PermSize=128M -XX:MaxPermSize=256M  -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.Beta1a.core/jbosstools-directory.xml  | tee "/tmp/eclipse.log.`date`.txt"

{color:red}*PENDING*{color}
./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.updatesite/extras/devstudio-directory.xml

{color:red}*PENDING*{color}
./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta1.extras/devstudio-directory.xml
{code}

Waiting for:

https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--central/ >=400
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ >=4191
https://hudson.qa.jboss.com/hudson/job/devstudio-5.0_trunk.updatesite/ >=1687
and
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--central/ >=43
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.aggregate/ >=80
https://hudson.qa.jboss.com/hudson/job/devstudio-5.0_stable_branch.updatesite/ >=67


                  
> add GWT to Extras site and point Central at our copy instead of live version on code.google.com
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-10967
>                 URL: https://issues.jboss.org/browse/JBIDE-10967
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central, GWT, updatesite, UpStream
>    Affects Versions: 3.3.0.Beta1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 3.3.0.Beta1
>
>
> Central already includes two features from Google's GWT/GPE offerings, which we can now mirror into Extras so that the version we provide is locked and only changes when WE decide to release a newer version. 
> Once 2 GWT/GPE features are in Extras, Central should pull from that URL instead of the upstream code.google.com one.

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