[ https://issues.jboss.org/browse/JBIDE-9686?page=com.atlassian.jira.plugin... ] Jiri Peterka updated JBIDE-9686: -------------------------------- Attachment: error-log.png -- 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-9686?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9686: -------------------------------------------- not blocking M3 -- 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-9686?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9686: -------------------------------------------- no it means some code is referencing it too early. The two other errors are related to GWT if i'm not mistaken (i.e. bug in code externally to JBT). -- 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-9686?page=com.atlassian.jira.plugin... ] Denis Golovin commented on JBIDE-9686: -------------------------------------- We should stop posting links to hudson builds, because they stop working after a while. -- 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-9686?page=com.atlassian.jira.plugin... ] Denis Golovin commented on JBIDE-9686: -------------------------------------- right, but I guess that means to keep too much history behind an clutter the hudson. Actually what Jiri posted is enough in this case, because there are no stacktraces for such errors. When fixing JBIDE-9675 I had to spend some time in debugger to find missing dependency. Problem is that plugin references Preferences/Properties category by its id, but didn't bother declare dependency to plugin that declares referenced category. -- 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-9686?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-9686: --------------------------------------- Fix Version/s: 3.3.0.Beta1 (was: 3.3.0.M4) Assignee: Alexey Kazakov (was: Max Rydahl Andersen) -- 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

[ https://issues.jboss.org/browse/JBIDE-9686?page=com.atlassian.jira.plugin... ] Alexey Kazakov updated JBIDE-9686: ---------------------------------- Priority: Major (was: Critical) -- 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

[ https://issues.jboss.org/browse/JBIDE-9686?page=com.atlassian.jira.plugin... ] Jiri Peterka commented on JBIDE-9686: ------------------------------------- Invalid preference page path: Speed Tracer Invalid preference page path: Web Toolkit stays on 3.3.0.M4 -- 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

[ https://issues.jboss.org/browse/JBIDE-9686?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9686: -------------------------------------------- so the problem is on GWT side? their plugins doesn't declare their dependencies on them, right? -- 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

[ https://issues.jboss.org/browse/JBIDE-9686?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-9686: --------------------------------- Fix Version/s: 3.3.0.Beta1 (was: 3.3.x) -- 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

[ https://issues.jboss.org/browse/JBIDE-9686?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-9686: ----------------------------------------- I looked into this issue and I'm pretty much still digging in the fog. I have no real clue what should be causing this, I can't follow Denis explanations. The only preferences related code that references gwt in some way is: http://anonsvn.jboss.org/repos/jbosstools/trunk/gwt/plugins/org.jboss.too... : {code} IEclipsePreferences preferences = projectScope.getNode(IGoogleEclipsePluginConstants.GDT_PLUGIN_ID); {code} {code} IClasspathEntry entry = JavaCore.newContainerEntry(new Path(IGoogleEclipsePluginConstants.GWT_CONTAINER_ID), false); ProjectUtils.addClasspathEntry(javaProject, entry, monitor); {code} There are no preferences cathegories nor other artifacts referenced in the plugin.xml. Is this code what causes these errors? -- 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

[ https://issues.jboss.org/browse/JBIDE-9686?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-9686 at 2/9/12 4:56 AM: ----------------------------------------------------------------- I looked into this issue and I'm pretty much still digging in the fog. I have no real clue what should be causing this, I can't follow Denis explanations. The only preferences related code that references gwt in some way is: http://anonsvn.jboss.org/repos/jbosstools/trunk/gwt/plugins/org.jboss.too... : {code} IEclipsePreferences preferences = projectScope.getNode(IGoogleEclipsePluginConstants.GDT_PLUGIN_ID); //com.google.gdt.eclipse.core {code} {code} EclipseUtil.addNatureToProject(javaProject.getProject(), IGoogleEclipsePluginConstants.GWT_NATURE); //com.google.gwt.eclipse.core.gwtNature {code} {code} IClasspathEntry entry = JavaCore.newContainerEntry(new Path(IGoogleEclipsePluginConstants.GWT_CONTAINER_ID), false); // com.google.gwt.eclipse.core.GWT_CONTAINER ProjectUtils.addClasspathEntry(javaProject, entry, monitor); {code} {code} monitor.subTask("Adding GWT Designer nature"); EclipseUtil.addNatureToProject(project.getProject(), IGWTDesignerConstants.GWTDESIGNER_NATURE); monitor.subTask("Adding GWT Designer builder"); EclipseUtil.addBuilderToProject(project.getProject(), IGWTDesignerConstants.GWTDESIGNER_BUILDER); {code} There are no preferences cathegories nor other artifacts referenced in the plugin.xml. Is this code what causes these errors? was (Author: adietish): I looked into this issue and I'm pretty much still digging in the fog. I have no real clue what should be causing this, I can't follow Denis explanations. The only preferences related code that references gwt in some way is: http://anonsvn.jboss.org/repos/jbosstools/trunk/gwt/plugins/org.jboss.too... : {code} IEclipsePreferences preferences = projectScope.getNode(IGoogleEclipsePluginConstants.GDT_PLUGIN_ID); {code} {code} IClasspathEntry entry = JavaCore.newContainerEntry(new Path(IGoogleEclipsePluginConstants.GWT_CONTAINER_ID), false); ProjectUtils.addClasspathEntry(javaProject, entry, monitor); {code} {code} monitor.subTask("Adding GWT Designer nature"); EclipseUtil.addNatureToProject(project.getProject(), IGWTDesignerConstants.GWTDESIGNER_NATURE); monitor.subTask("Adding GWT Designer builder"); EclipseUtil.addBuilderToProject(project.getProject(), IGWTDesignerConstants.GWTDESIGNER_BUILDER); {code} There are no preferences cathegories nor other artifacts referenced in the plugin.xml. Is this code what causes these errors? -- 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

[ https://issues.jboss.org/browse/JBIDE-9686?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-9686: ----------------------------------------- @Denis: concretely, is the code printed above the reason for the errors? -- 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

[ https://issues.jboss.org/browse/JBIDE-9686?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-9686: --------------------------------- Assignee: Andre Dietisheim (was: Denis Golovin) Back to Andre with note that to fix this issue we can add dependency to com.google.gdt.eclipse.suite to GWT integration plugin. -- 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

[ https://issues.jboss.org/browse/JBIDE-9686?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-9686: ------------------------------------ Attachment: gdt-suite-dependency.patch committed to TRUNK, patch for Beta1 attached. @Max: please review and approve/reject patch for Beta1 -- 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

[ https://issues.jboss.org/browse/JBIDE-9686?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-9686: ----------------------------------------- in the Manifest of the suite plugin I found the following list of dependencies: {quote} com.google.appengine.eclipse.core, com.google.gdt.eclipse.appsmarketplace, com.google.gdt.eclipse.login, com.google.gdt.eclipse.managedapis, com.google.gwt.eclipse.core, com.google.gwt.eclipse.oophm, org.eclipse.core.expressions, org.eclipse.core.filesystem, org.eclipse.core.runtime.compatibility, org.eclipse.core.variables, org.eclipse.debug.ui, org.eclipse.jdt.core, org.eclipse.jdt.debug.ui, org.eclipse.jdt.launching, org.eclipse.jdt.ui, org.eclipse.ui, org.eclipse.ui.browser, org.eclipse.ui.console, org.eclipse.ui.forms, org.eclipse.ui.ide, org.eclipse.wst.server.core {quote} -- 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

[ https://issues.jboss.org/browse/JBIDE-9686?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9686: -------------------------------------------- +1 for patch if this does not force installation of Google App Engine SDK/dependencies -- 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

[ https://issues.jboss.org/browse/JBIDE-9686?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-9686: ----------------------------------------- to me com.google.appengine.eclipse.core definitely is about google appengine (looking at the classes, etc.). The most evidence to me is in the following entry in the plugin.xml: {quote} <command commandId="com.google.appengine.eclipse.core.deployToGoogle" icon="icons/ae-deploy_16x16.png" label="Deploy to App Engine..." {quote} It obviously defines a command to deploy to app engine. -- 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

[ https://issues.jboss.org/browse/JBIDE-9686?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9686: -------------------------------------------- @Denis: +1 -- 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

[ https://issues.jboss.org/browse/JBIDE-9686?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-9686: ----------------------------------- I trust you mean the first blue build from: https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ >=4496 which would put the bits here: http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ (currently has H4471, needs H4496 or later) -- 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

[ https://issues.jboss.org/browse/JBIDE-9686?page=com.atlassian.jira.plugin... ] Denis Golovin edited comment on JBIDE-9686 at 4/5/12 6:02 PM: -------------------------------------------------------------- even 4471 should be fine because commit was done in February https://source.jboss.org/changelog/JBossTools?cs=38929 was (Author: dgolovin): even 4471 should be fine because commit was done in February -- 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