[ https://issues.jboss.org/browse/JBIDE-8145?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-8145: ----------------------------------- What happens if the user manually selects the GWT SDK for installation in parallel (or before) installing the JBT GWT stuff? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8145?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-8145: ----------------------------------------- I can reproduce this unfortunately. The GWT bundle is not pulled from our update site (see JBIDE-8145) Afaik the gwt plugin is present on our update site (see https://issues.jboss.org/browse/JBIDE-7956?focusedCommentId=12586438&...) and p2 is told to pull optional dependencies:. https://bugs.eclipse.org/bugs/show_bug.cgi?id=247099#c18 "...will always try to resolve the optional dependencies if they are available. This causes p2 to look for the optional dependencies and try to pull them in if they can be installed. If they can not be installed then they will be discarded and the system will still succeed to resolve" I need to check with nick. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8145?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-8145: ----------------------------------------- I retested the whole things and found out that the following google plugins get pulled from our update site (no gwt update site added!): * com.google.gdt.eclipse.core_1.4.2.v201012211742 * com.google.gdt.eclipse.platform_1.4.2.v201012211742 * com.google.gdt.eclipse.platform.e36_1.4.2.v201012211742 * com.google.gdt.eclipse.platform.shared_1.4.2.v201012211742 * com.google.gwt.eclipse.core_1.4.2.v201012211742 * com.google.gwt.eclipse.sdkbundle.2.1.1_2.1.1.v201012170127 The following are missing: * com.google.appengine.eclipse.core_1.4.2.v201012211742 * com.google.gdt.eclipse.maven_1.4.2.v201012211742 * com.google.gdt.eclipse.suite_1.4.2.v201012211742 * com.google.gwt.eclipse.oophm_1.4.2.v201012211742 I guess at least the com.google.gdt.eclipse.suite and com.google.gwt.eclipse.oophm should get installed. I might miss depencies in my plugin. I'll further investigate. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8145?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-8145: ----------------------------------------- The proprietary licence google applies to their plugin unfortunately prevents us from doing that (http://code.google.com/intl/de-DE/eclipse/terms.html, Section 5.3). I therefore removed the depdendency to their sdk and dropped any installation ease and guard. You'll have to install the google plugins manually in a first step. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8145?page=com.atlassian.jira.plugin... ] Andre Dietisheim resolved JBIDE-8145. ------------------------------------- Resolution: Won't Fix -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira