|
|
|
|
Re: Build state machine has not been initialized [message #505840 is a reply to message #492929] |
Tue, 05 January 2010 05:28 |
Eclipse User |
|
|
|
Originally posted by: krischik.users.sourceforge.net
Diego Madruga Sandin schrieb:
> This problem was fixed during the 1.0.1 release. Could you try to import
> your projects into a clean workspace and report if the issue still occurs?
I have got the same problem and I must have created a half a dozed
"clean" workspaces today.
Honestly this is a real pain. Being a programmer myself: if the state
machine is not initialized: Why not initialize it instead of a useless
error message?
Note 1: All error messages without a proper course of action to rectify
the problem are useless.
Also a "clean" / "clean all" should initialize the state machine as well.
And why is this error message appearing when "automated build" is
switched off? If I did not request a build no preprocessing should
happen, shouldn't it?
Regards
Martin
--
mailto://krischik@users.sourceforge.net
Ada programming at: http://ada.krischik.com
|
|
|
Re: Build state machine has not been initialized [message #509927 is a reply to message #505840] |
Mon, 25 January 2010 19:16 |
|
I'm experiencing this problem as well, first with 1.0 and then after updating to 1.0.1. For various reasons creating a new workspace is going to cost me a lot of time as well--enough that I would consider manually hacking the internal configuration of my workspace if I knew what to look for. If someone who knows the nature of the bug can suggest a way to give this a try, please do.
David Beers
MapQuest
|
|
|
Re: Build state machine has not been initialized [message #510237 is a reply to message #509927] |
Tue, 26 January 2010 20:07 |
|
Follow-up: I checked out a fresh working copy from SVN, recreating the project in a new workspace and still get the same message.
Errors during build.
Errors running builder 'Preverification Builder' on project 'Midlet_MQ4M'.
Build state machine has not been initialized.
I've been using MTJ and the project in question daily for quite some time and can't fathom what suddenly caused this error to manifest.
Checking the Eclipse logs I see this entry prior to the error in question:
!ENTRY org.eclipse.mtj.core 4 0 2010-01-26 12:12:56.347
!MESSAGE Invalid MTJ Project.
!STACK 0
java.lang.IllegalArgumentException: Invalid MTJ Project.
at org.eclipse.mtj.internal.core.build.MTJBuildProperties.<init >(Unknown Source)
at org.eclipse.mtj.internal.core.build.MTJBuildProperties.getBu ildProperties(Unknown Source)
at org.eclipse.mtj.internal.core.util.MTJBuildPropertiesResourc eListener.updateBuildProperties(Unknown Source)
at org.eclipse.mtj.internal.core.util.MTJBuildPropertiesResourc eListener.resourceChanged(Unknown Source)
at org.eclipse.core.internal.events.NotificationManager$2.run(N otificationManager.java:288)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.internal.events.NotificationManager.notify( NotificationManager.java:282)
at org.eclipse.core.internal.events.NotificationManager.broadca stChanges(NotificationManager.java:148)
at org.eclipse.core.internal.resources.Workspace.broadcastPostC hange(Workspace.java:313)
at org.eclipse.core.internal.resources.Workspace.endOperation(W orkspace.java:1022)
at org.eclipse.core.internal.resources.Resource.refreshLocal(Re source.java:1497)
at org.eclipse.core.internal.resources.Project.open(Project.jav a:891)
at org.eclipse.core.internal.resources.Project.open(Project.jav a:911)
at org.eclipse.jdt.internal.ui.wizards.buildpaths.BuildPathsBlo ck.createProject(BuildPathsBlock.java:694)
at org.eclipse.jdt.ui.wizards.JavaCapabilityConfigurationPage.c reateProject(JavaCapabilityConfigurationPage.java:251)
at org.eclipse.jdt.ui.wizards.NewJavaProjectWizardPageTwo.updat eProject(NewJavaProjectWizardPageTwo.java:233)
at org.eclipse.jdt.ui.wizards.NewJavaProjectWizardPageTwo.acces s$2(NewJavaProjectWizardPageTwo.java:200)
at org.eclipse.jdt.ui.wizards.NewJavaProjectWizardPageTwo$1$Upd ateRunnable.run(NewJavaProjectWizardPageTwo.java:161)
at org.eclipse.ui.actions.WorkspaceModifyDelegatingOperation.ex ecute(WorkspaceModifyDelegatingOperation.java:69)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(Worksp aceModifyOperation.java:104)
at org.eclipse.core.internal.resources.Workspace.run(Workspace. java:1800)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(Workspac eModifyOperation.java:116)
at org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:121)
How can I help the developers characterize and resolve this critical bug? Until a fix is found I'm unable to build and run/debug our app in Eclipse. Were it not for dependencies on another project that is Maven-managed and links to stuff in a private repository, I would share it for someone to inspect. But if I'm able to reproduce it in a simpler sample project I'll certainly do so. Again, suggestions on modifying the internal configs or any other temporary workaround are welcome.
David Beers
MapQuest
[Updated on: Tue, 26 January 2010 20:08] Report message to a moderator
|
|
|
|
Re: Build state machine has not been initialized [message #510254 is a reply to message #510238] |
Tue, 26 January 2010 22:43 |
|
I took a stab at your suggestion, Ugo, but for for reasons peculiar to our build configuration it will be an extremely painful option to carry out. Reverting to MTJ v0.9.1 required a little fiddling around but it didn't take too long and seems to solve the problem, so that's what I have done for the time being.
David Beers
MapQuest
|
|
|
Re: Build state machine has not been initialized [message #521622 is a reply to message #492035] |
Thu, 18 March 2010 10:34 |
Mario Balaban Messages: 5 Registered: July 2009 |
Junior Member |
|
|
This is a piece of the .log file from the workspace:
!SESSION 2010-03-18 11:21:21.808 -----------------------------------------------
eclipse.buildId=
java.version=1.6.0_14
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=it_IT
Framework arguments: -product org.eclipse.epp.package.jee.product -showlocation
Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.jee.product -clean -showlocation
!ENTRY org.eclipse.core.resources 4 2 2010-03-18 11:23:24.249
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
!STACK 1
org.eclipse.core.runtime.CoreException: Build state machine has not been initialized.
at org.eclipse.mtj.internal.core.build.BuildStateMachine.change State(Unknown Source)
at org.eclipse.mtj.internal.core.build.MTJIncrementalProjectBui lder.onStateEnter(Unknown Source)
at org.eclipse.mtj.internal.core.build.MTJIncrementalProjectBui lder.build(Unknown Source)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildMan ager.java:627)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:170)
at org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:201)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:253)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:256)
at org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:218)
at org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:360)
at org.eclipse.core.internal.resources.Project$1.run(Project.ja va:523)
at org.eclipse.core.internal.resources.Workspace.run(Workspace. java:1800)
at org.eclipse.core.internal.resources.Workspace.run(Workspace. java:1782)
at org.eclipse.core.internal.resources.Project.internalBuild(Pr oject.java:502)
at org.eclipse.core.internal.resources.Project.build(Project.ja va:94)
at org.eclipse.mtj.internal.core.project.midp.MidletSuiteProjec t.createPackage(Unknown Source)
at org.eclipse.mtj.internal.ui.actions.packaging.AbstractCreate PackageAction.createPackageForProject(Unknown Source)
at org.eclipse.mtj.internal.ui.actions.packaging.AbstractCreate PackageAction.access$0(Unknown Source)
at org.eclipse.mtj.internal.ui.actions.packaging.AbstractCreate PackageAction$1.run(Unknown Source)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.mtj.internal.ui.actions.packaging.AbstractCreate PackageAction.doPackageCreation(Unknown Source)
at org.eclipse.mtj.internal.ui.actions.packaging.AbstractCreate PackageAction.run(Unknown Source)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginActi on.java:251)
at org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3493)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3112)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 21)
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(Work bench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.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(EclipseS tarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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)
!SUBENTRY 1 org.eclipse.mtj.core 4 999 2010-03-18 11:23:24.251
!MESSAGE Build state machine has not been initialized.
!SUBENTRY 1 org.eclipse.mtj.core 4 999 2010-03-18 11:23:24.251
!MESSAGE Build state machine has not been initialized.
Any solutions?
[Updated on: Thu, 18 March 2010 10:51] Report message to a moderator
|
|
|
Re: Build state machine has not been initialized [message #522498 is a reply to message #521622] |
Mon, 22 March 2010 19:16 |
Eclipse User |
|
|
|
Originally posted by: krischik.users.sourceforge.net
Am 18.03.2010, 11:34 Uhr, schrieb Mario Balaban <extremepredator@mail.ru>:
> Then I restarted eclipse with the same workspace, made a modification to
> the source (modified a comment) and tried to recreate the package. And
> voila ! Build state machine has not been initialized !
This is a painful and persistent one. I for once changed to Maven based
builds in the end and never looked back.
Regards
Martin
--
Martin Krischik
|
|
|
Re: Build state machine has not been initialized [message #522499 is a reply to message #521622] |
Mon, 22 March 2010 19:20 |
Eclipse User |
|
|
|
Originally posted by: krischik.users.sourceforge.net
Am 18.03.2010, 11:34 Uhr, schrieb Mario Balaban <extremepredator@mail.ru>:
> Then I restarted eclipse with the same workspace, made a modification to
> the source (modified a comment) and tried to recreate the package. And
> voila ! Build state machine has not been initialized !
This is a painful and persisted one.
> Any solutions?
I for one changed to Maven based builds in the end and I never looked
back. The Maven plugin for Java ME works great - I can even build on Mac
OS X.
Martin
--
Martin Krischik
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05154 seconds