| [acceleo] Source context menu not showing up during Android Tutorial [message #560043] |
Mon, 20 September 2010 21:45  |
 Glenview Jeff
Messages: 79
Registered: September 2010 |
Member |
|
|
I'm trying to go through the Android Tutorial. So far so good, except that I reached section "Quick hierarchy tree."
When trying follow the step: "In the modules that contains Widgets declarations or calls, select them and then right-click and run: Source > As For/If."
I noticed there is no "Source" context menu after selecting the text. Eclipse is correctly using the acceleo template editor (I get syntax highlighting, etc.)
I did notice the following new error: Build path specifies execution environment J2SE-1.5. There are no JREs installed in the workspace that are strictly compatible with this environment. I'm guessing I need to go find a new JRE. I'll update this message after I go down that path.
Thanks!
[Updated on: Mon, 20 September 2010 21:56] Report message to a moderator |
|
|
| Re: [acceleo] Source context menu not showing up during Android Tutorial [message #560074 is a reply to message #560043] |
Tue, 21 September 2010 07:03  |
|
Hi,
The JRE-thing is just a warning. It is best to have a Jre 6 for Java 6 projects and a Jre 5 for Java 5 projects. It is a good practice to prevent problems. It is not linked with Acceleo except that Acceleo needs Java 5 but using it with Java 6 does not create problems that I'm aware of (I do it half the time). For your missing "source menu", are you using the Java or Acceleo perspective ? Did you see any other problems with the Acceleo editor ? Does this happens even on a simple new Acceleo project ?
It should look like this on a new project:
Stephane Begaudeau, Obeo
|
|
|
|
|
|
| Re: [acceleo] Source context menu not showing up during Android Tutorial [message #636265 is a reply to message #628711] |
Sat, 30 October 2010 03:54 |
Glenview Jeff
Messages: 79
Registered: September 2010 |
Member |
|
|
Update: I just came back to Acceleo and still have been unable to get the source menu to appear. (I edited this post because I forgot what the original problem was--it ends up that it's exactly as before.) I may try a fresh Eclipse installation. Some other useful notes though for others getting started:
I did notice when trying this for a second time that I was running out of memory, so I assumed that it is likely that I didn't have the spawned Acceleo Eclipse instance configured with enough additional memory.
I'm posting the steps here in case someone else wants to know how to alleviate this. I suspect there's a way to launch the Acceleo Eclipse instance directly rather than from a base Eclipse, but I haven't looked into how to do this yet. It seems that the spawned Eclipses don't pay attention to the Eclipse.ini settings for memory handling.
When running the new Eclipse session at the following step in the tutorial: "2. Right-Click on the Eclipse Application item and select New. Rename the configuration, choose a location, and run it."
Increase the memory using the Arguments tab in the Run Configuration window for the newly created run configuration. I used -Xms40m -Xmx512m -XX:PermSize=512m -XX:MaxPermSize=1024m
Also note that I created project from existing source (the zip file included in the tutorial) in these steps: "The Android Project - In the new Eclipse Runtime environment, you are going to create a new Android Project." (Make sure to unzip the example zip code on my desktop or somewhere besides the workspace because Eclipse copies it to the workspace when you select "from existing code"
[Updated on: Sat, 30 October 2010 04:17] Report message to a moderator |
|
|
|
|
| Re: [acceleo] Source context menu not showing up during Android Tutorial [message #636295 is a reply to message #636269] |
Sat, 30 October 2010 13:43 |
Glenview Jeff
Messages: 79
Registered: September 2010 |
Member |
|
|
Update: I just did a fresh Helios (3.6) install, installed Acceleo from the Install Modeling Components menu item, and the top menu problem persists there as well, but the context menu options are available, so at least its now functional and I can proceed.
My only concern now is that the most recent Android SDK requires no later than Eclipse 3.5. It will be a hassle to switch back and forth between Eclipse platforms.
When I ask Eclipse 3.5 to check for updates, it reports everything is up to date, yet Acceleo is stuck at 0.8.1. I know that Acceleo is now up to 3.1. Is 0.8.1 the latest version that is backwards compatible with Eclipse 3.5?
[Updated on: Sat, 30 October 2010 14:04] Report message to a moderator |
|
|
| Re: [acceleo] Source context menu not showing up during Android Tutorial [message #636317 is a reply to message #636295] |
Sat, 30 October 2010 19:42 |
|
This is a multi-part message in MIME format.
--------------050308070300050106080807
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi Jeff,
I seem to have missed some of the mails along the way but ... When you
have "missing" actions, are they _all_ missing (quick outline, source
menu, refactor menu, F3 to open declarations...) or are you just missing
some?
If they are _all_ missing, are you in either the Acceleo or Java
perspective? I know we don't activate our action sets outside of these two.
Laurent Goubet
Obeo
Jeff A wrote:
> Update: I just did a fresh Helios (3.6) install, installed Acceleo from
> the Install Modeling Components menu item, and the problem persists
> there as well.
--------------050308070300050106080807
Content-Type: text/x-vcard; charset=utf-8;
name="laurent_goubet.vcf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="laurent_goubet.vcf"
YmVnaW46dmNhcmQNCmZuOkxhdXJlbnQgR291YmV0DQpuOkdvdWJldDtMYXVy ZW50DQpvcmc6
PGEgaHJlZj0iaHR0cDovL3d3dy5vYmVvLmZyIj5PYmVvPC9hPg0KZW1haWw7 aW50ZXJuZXQ6
bGF1cmVudC5nb3ViZXRAb2Jlby5mcg0KdXJsOmh0dHA6Ly93d3cub2Jlby5m cg0KdmVyc2lv
bjoyLjENCmVuZDp2Y2FyZA0KDQo=
--------------050308070300050106080807--
|
|
|
|
|
| Re: [acceleo] Source context menu not showing up during Android Tutorial [message #636353 is a reply to message #636320] |
Sun, 31 October 2010 10:56 |
|
| Jeff A wrote on Sat, 30 October 2010 16:46 | Based on what (you?) said in my bug report, I'm just going to use Acceleo 3.x., especially if it's supported in Galileo. I can't think of any good reason to use the old version of Acceleo if these problems are fixed in 3.x.
Thanks!
|
Yup, that would be me  . Didn't realize "Jeff A" and the bugzilla "anonymous" were the same ^^. And yes, we strive to maintain compatibility throughout the different Eclipse versions for Acceleo (see also the Acceleo wiki).
Your stack trace would indicate that some of your "mtl" modules haven't been recompiled with the latest version of Acceleo you installed, as it is still trying to find the 0.8.0 package. Could you try using "Project => Clean", to clean all of your projects and force the recompilation of all Acceleo modules?
Laurent Goubet
Obeo
|
|
|
|
| Re: [acceleo] Source context menu not showing up during Android Tutorial [message #636402 is a reply to message #636374] |
Mon, 01 November 2010 02:40 |
Glenview Jeff
Messages: 79
Registered: September 2010 |
Member |
|
|
Hi Laurent:
I just ran into a new problem when trying to work with my own code. I created the a metamodel and generated an editor, etc. and opened the new Eclipse environment with the metamodel's new editor.
Another problem I noticed is that I can't create a new
I created a new model file with the EMF creation wizard. However, the "new child" submenu is missing. In the tutorial project (in a different Eclipse instance) I can see the new child submenu just fine.
One other bit of info that might help the troubleshooting is that the icons for the ".android" file model editor and the model component icons are different than the model editor from the tutorial for some reason. The icons from my project are more plain and blue/white instead of gold, blue, and white.
Here are some messages from the error log that might indicate the problem:
!ENTRY com.zoomabug.flashcards.model.editor 2 0 2010-10-31 21:10:43.671
!MESSAGE A resource exists with a different case: '/com.zoomabug.flashcards/Model'.
!STACK 0
org.eclipse.emf.ecore.resource.Resource$IOWrappedException: A resource exists with a different case: '/com.zoomabug.flashcards/Model'.
at org.eclipse.emf.ecore.resource.impl.PlatformResourceURIHandlerImpl$PlatformResourceOutputStream.createContainer(PlatformResourceURIHandlerImpl.java:81)
at org.eclipse.emf.ecore.resource.impl.PlatformResourceURIHandlerImpl$PlatformResourceOutputStream.flush(PlatformResourceURIHandlerImpl.java:108)
at org.eclipse.emf.ecore.resource.impl.PlatformResourceURIHandlerImpl$PlatformResourceOutputStream.close(PlatformResourceURIHandlerImpl.java:90)
at org.eclipse.emf.ecore.resource.impl.PlatformResourceURIHandlerImpl$WorkbenchHelper$1.close(PlatformResourceURIHandlerImpl.java:172)
at org.eclipse.emf.ecore.resource.impl.ResourceImpl.save(ResourceImpl.java:997)
at com.zoomabug.flashcards.flashcards.presentation.FlashcardsModelWizard$1.execute(FlashcardsModelWizard.java:263)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:944)
at com.zoomabug.flashcards.flashcards.presentation.FlashcardsModelWizard.performFinish(FlashcardsModelWizard.java:274)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:752)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:373)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:253)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:273)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Caused by: org.eclipse.core.internal.resources.ResourceException: A resource exists with a different case: '/com.zoomabug.flashcards/Model'.
at org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:307)
at org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:285)
at org.eclipse.core.internal.resources.Folder.assertCreateRequirements(Folder.java:29)
at org.eclipse.core.internal.resources.Folder.create(Folder.java:88)
at org.eclipse.core.internal.resources.Folder.create(Folder.java:118)
at org.eclipse.emf.ecore.resource.impl.PlatformResourceURIHandlerImpl$PlatformResourceOutputStream.createContainer(PlatformResourceURIHandlerImpl.java:77)
... 58 more
!SESSION 2010-10-31 21:30:32.976 -----------------------------------------------
eclipse.buildId=M20100211-1343
java.version=1.6.0_21
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.sdk.ide
Command-line arguments: -product org.eclipse.sdk.ide -data D:\My Documents\Software Development\Eclipse Workspaces\GTD Development/../flashcards-modeling -dev file:D:/My Documents/Software Development/Eclipse Workspaces/GTD Development/.metadata/.plugins/org.eclipse.pde.core/Android (Acceleo)/dev.properties -os win32 -ws win32 -arch x86_64
!ENTRY org.eclipse.update.configurator 4 0 2010-10-31 21:30:41.375
!MESSAGE Can't find bundle for base name feature, locale en_US
!ENTRY org.eclipse.update.configurator 4 0 2010-10-31 21:30:41.604
!MESSAGE Can't find bundle for base name feature, locale en_US
!ENTRY org.eclipse.update.configurator 4 0 2010-10-31 21:30:41.641
!MESSAGE Can't find bundle for base name feature, locale en_US
!ENTRY org.eclipse.update.configurator 4 0 2010-10-31 21:30:41.737
!MESSAGE Can't find bundle for base name feature, locale en_US
!ENTRY org.eclipse.ui.workbench 2 0 2010-10-31 21:30:42.284
!MESSAGE A handler conflict occurred. This may disable some commands.
!SUBENTRY 1 org.eclipse.ui.workbench 2 0 2010-10-31 21:30:42.284
!MESSAGE Conflict for 'AUTOGEN:::com.soyatec.uml.std.ui.check.diagram/com.soyatec.uml.std.ui.actions.check.diagram':
HandlerActivation(commandId=AUTOGEN:::com.soyatec.uml.std.ui.check.diagram/com.soyatec.uml.std.ui.actions.check.diagram,
handler=ActionDelegateHandlerProxy(null,com.soyatec.uml.std.external.UMLCheckDiagramAction),
expression=WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@6a48ffbc),sourcePriority=16384)
HandlerActivation(commandId=AUTOGEN:::com.soyatec.uml.std.ui.check.diagram/com.soyatec.uml.std.ui.actions.check.diagram,
handler=ActionDelegateHandlerProxy(null,com.soyatec.uml.std.external.UMLCheckDiagramAction),
expression=WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@6a48ffbc),sourcePriority=16384)
!ENTRY org.eclipse.core.resources 8 2 2010-10-31 21:30:44.098
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
!STACK 1
org.eclipse.core.runtime.CoreException: Project target not loaded yet.
at com.android.ide.eclipse.adt.internal.build.BaseBuilder.stopBuild(Unknown Source)
at com.android.ide.eclipse.adt.internal.build.BaseBuilder.abortOnBadSetup(Unknown Source)
at com.android.ide.eclipse.adt.internal.build.ResourceManagerBuilder.build(Unknown Source)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:627)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!SUBENTRY 1 com.android.ide.eclipse.adt 8 0 2010-10-31 21:30:44.099
!MESSAGE Project target not loaded yet.
!SUBENTRY 1 com.android.ide.eclipse.adt 8 0 2010-10-31 21:30:44.099
!MESSAGE Project target not loaded yet.
!ENTRY org.eclipse.core.resources 8 2 2010-10-31 21:30:44.116
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
!STACK 1
org.eclipse.core.runtime.CoreException: Project target not loaded yet.
at com.android.ide.eclipse.adt.internal.build.BaseBuilder.stopBuild(Unknown Source)
at com.android.ide.eclipse.adt.internal.build.BaseBuilder.abortOnBadSetup(Unknown Source)
at com.android.ide.eclipse.adt.internal.build.PreCompilerBuilder.build(Unknown Source)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:627)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!SUBENTRY 1 com.android.ide.eclipse.adt 8 0 2010-10-31 21:30:44.116
!MESSAGE Project target not loaded yet.
!SUBENTRY 1 com.android.ide.eclipse.adt 8 0 2010-10-31 21:30:44.116
!MESSAGE Project target not loaded yet.
[Updated on: Mon, 01 November 2010 02:56] Report message to a moderator |
|
|
|
|
|
|
| Re: [acceleo] Source context menu not showing up during Android Tutorial [message #637642 is a reply to message #560043] |
Mon, 08 November 2010 08:24 |
|
Hi jeff,
The wizards and metamodel URI themselves are provided by the metamodel plugins. "leftover" metamodels mean that you still have the plugins :
- in the "parent" Eclipse workspace
- installed in your Eclipse
When you say you deleted them, did you indeed remove them from your workspace? And if you had deployed them, did you also uninstall them from your Eclipse ?
Laurent Goubet
Obeo
|
|
|
|
Powered by
FUDForum. Page generated in 0.05526 seconds
] 
Search
Help
Register
Login
Home
