[JBoss JIRA] (JBDS-2486) Investigate use of GWT/GPE 3.2.0.v201302131858-rel-r42 in Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2486?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2486 at 3/11/13 7:53 PM:
-----------------------------------------------------------
This change breaks our Central connectors too:
{code:title=when installing into JBDS 7.0.0.Alpha1 from 7.0-development site}
Problems occurred while performing installation: The following connectors are not available:
Google Plugin + Web Toolkit (id=com.google.gwt.eclipse.sdkbundle.e42.feature.feature.group, site=https://devstudio.jboss.com/updates/7.0-development/central/core/),
Google Web Toolkit Designer (id=com.google.gwt.eclipse.sdkbundle.e42.feature.feature.group, site=https://devstudio.jboss.com/updates/7.0-development/central/core/)
The following connectors are not available:
Google Plugin + Web Toolkit (id=com.google.gwt.eclipse.sdkbundle.e42.feature.feature.group, site=https://devstudio.jboss.com/updates/7.0-development/central/core/),
Google Web Toolkit Designer (id=com.google.gwt.eclipse.sdkbundle.e42.feature.feature.group, site=https://devstudio.jboss.com/updates/7.0-development/central/core/)
{code}
was (Author: nickboldt):
This change breaks out Central connectors too:
{code:title=when installing into JBDS 7.0.0.Alpha1 from 7.0-development site}
Problems occurred while performing installation: The following connectors are not available:
Google Plugin + Web Toolkit (id=com.google.gwt.eclipse.sdkbundle.e42.feature.feature.group, site=https://devstudio.jboss.com/updates/7.0-development/central/core/),
Google Web Toolkit Designer (id=com.google.gwt.eclipse.sdkbundle.e42.feature.feature.group, site=https://devstudio.jboss.com/updates/7.0-development/central/core/)
The following connectors are not available:
Google Plugin + Web Toolkit (id=com.google.gwt.eclipse.sdkbundle.e42.feature.feature.group, site=https://devstudio.jboss.com/updates/7.0-development/central/core/),
Google Web Toolkit Designer (id=com.google.gwt.eclipse.sdkbundle.e42.feature.feature.group, site=https://devstudio.jboss.com/updates/7.0-development/central/core/)
{code}
> Investigate use of GWT/GPE 3.2.0.v201302131858-rel-r42 in Central
> -----------------------------------------------------------------
>
> Key: JBDS-2486
> URL: https://issues.jboss.org/browse/JBDS-2486
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, central
> Affects Versions: 7.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 7.0.0.Alpha2
>
>
> New 3.2.0 mirrors:
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.2.0.v2013...
> https://devstudio.jboss.com/updates/requirements/gwt/3.2.0.v201302131858-...
> New composites:
> http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.1/
> https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.1/
> Note that at least one IU had been renamed:
> OLD: com.google.gwt.eclipse.sdkbundle.e42.feature
> NEW: com.google.gwt.eclipse.sdkbundle.feature
--
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
13 years, 1 month
[JBoss JIRA] (JBDS-2469) Cannot install all extras from central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2469?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2469 at 3/11/13 7:45 PM:
-----------------------------------------------------------
Link to JBIDE-13754 caused by me providing bad/incomplete information to Len about how to test Central. :(
was (Author: nickboldt):
Link to JBIDE-13754 caused by me providing bad/imcomplete information to Len about how to test Central. :(
> Cannot install all extras from central
> --------------------------------------
>
> Key: JBDS-2469
> URL: https://issues.jboss.org/browse/JBDS-2469
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.0.0.Alpha1
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Fix For: 7.0.0.Alpha2
>
> Attachments: central-install.png, central-install2.png
>
>
> devstudio-directory.xml is:
> <directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/">
> <entry url="plugins/com.jboss.jbds.central.discovery_7.0.0.Alpha1-v20130211-0546-B6.jar" permitCategories="true"/>
> </directory>
> I selected all components in the list and could not complete the install. Please see screenshots.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13335) remove Juno SR1+ performance fix from Central
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13335?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-13335:
------------------------------------
Affects: Release Notes
> remove Juno SR1+ performance fix from Central
> ----------------------------------------------
>
> Key: JBIDE-13335
> URL: https://issues.jboss.org/browse/JBIDE-13335
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Labels: respin-a
> Fix For: 4.0.1.Final
>
> Attachments: JBIDE13335.patch.JBDS6.0.1.txt
>
>
> For our 4.0.1 release, we will not need this performance tweak because we'll be including Juno SR2, which already includes the patched versions of Eclipse jars.
> Need to therefore, for JBT 4.0.1 and JBDS 6.0.1:
> a) remove the requirements/eclipse/4.2.1.v20121122-0007-patches/ site from Central composite sites (2 places)
> b) remove the connector from discovery plugins' plugin.xml (2 files)
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13767) JBoss Tools 4.1 Central points to JBoss Tools 4.0's central site
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13767?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-13767:
----------------------------------------
Fix Version/s: 4.1.0.Alpha2
(was: 4.1.0.Alpha1)
since alpha1 is already released this is alpha2.
> JBoss Tools 4.1 Central points to JBoss Tools 4.0's central site
> ----------------------------------------------------------------
>
> Key: JBIDE-13767
> URL: https://issues.jboss.org/browse/JBIDE-13767
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 4.1.0.Alpha2
>
>
> Due to some ugly hardcoding in the project examples plugin, we forgot to update JBT Central to pull from the new Kepler site.
> Thus:
> {code:title=examples/plugins/org.jboss.tools.project.examples/src/org/jboss/tools/project/examples/configurators/DefaultJBossCentralConfigurator.java}
> 44- // TODO: when moving to Kepler, use /development/kepler/ then later /stable/kepler/
> 45: private static final String JBOSS_DIRECTORY_URL_DEFAULT = "http://download.jboss.org/jbosstools/updates/stable/juno/jbosstools-direc..."; //$NON-NLS-1$
> 46-
> 47- // see pom.xml for actual value -- this is passed it at build-time via Maven
> {code}
> {code:title=examples/plugins/org.jboss.tools.project.examples/pom.xml}
> 13- <properties>
> 14- <!-- TODO: when moving to Kepler, use /development/kepler/ then later /stable/kepler/ -->
> 15: <jboss.discovery.directory.url>http://download.jboss.org/jbosstools/updates/stable/juno/jbosstools-direc...</jboss.discovery.directory.url>
> 16- </properties>
> 17-
> {code}
> So... oops.
> We should really figure out a better way to externalize this.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13767) JBoss Tools 4.1 Central points to JBoss Tools 4.0's central site
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13767?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13767:
---------------------------------------------
I misread the snippets - I can see it is statically replaced at build time. Not sure what else can be done ?
> JBoss Tools 4.1 Central points to JBoss Tools 4.0's central site
> ----------------------------------------------------------------
>
> Key: JBIDE-13767
> URL: https://issues.jboss.org/browse/JBIDE-13767
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 4.1.0.Alpha1
>
>
> Due to some ugly hardcoding in the project examples plugin, we forgot to update JBT Central to pull from the new Kepler site.
> Thus:
> {code:title=examples/plugins/org.jboss.tools.project.examples/src/org/jboss/tools/project/examples/configurators/DefaultJBossCentralConfigurator.java}
> 44- // TODO: when moving to Kepler, use /development/kepler/ then later /stable/kepler/
> 45: private static final String JBOSS_DIRECTORY_URL_DEFAULT = "http://download.jboss.org/jbosstools/updates/stable/juno/jbosstools-direc..."; //$NON-NLS-1$
> 46-
> 47- // see pom.xml for actual value -- this is passed it at build-time via Maven
> {code}
> {code:title=examples/plugins/org.jboss.tools.project.examples/pom.xml}
> 13- <properties>
> 14- <!-- TODO: when moving to Kepler, use /development/kepler/ then later /stable/kepler/ -->
> 15: <jboss.discovery.directory.url>http://download.jboss.org/jbosstools/updates/stable/juno/jbosstools-direc...</jboss.discovery.directory.url>
> 16- </properties>
> 17-
> {code}
> So... oops.
> We should really figure out a better way to externalize this.
--
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
13 years, 1 month