| Build state machine has not been initialized [message #32286] |
Mon, 13 July 2009 18:26  |
Eclipse User |
|
|
|
Hi all,
I'm in a project with AspectJ (AJDT 2.0) + MTJ 1.0 (Pulsar), trying to do
some stuff with J2ME.
The configuration of the Eclipse's is the following:
Aspectj project enabled.
Put Aspects in classpath when being asked.
Preverification active, packaging unactive.
There are no errors in java code. And with this conf, the virtual machine
can't locate aspects classes when try tu run/debug my app in the emulator.
In mtj 0.9 I had to put aspectjrt library in the aspect inpath. But if I
do so with mtj 1.0 I got the error "build state machine has not been
initialized".
I have rolled back to mtj 0.9.1 :( .
Somebody knows about this error? How to solve it? I'm wrong with the
configuration?
Thanks in advance,
Victor Llorens
|
|
|
|
|
|
|
|
| Re: Build state machine has not been initialized [message #33427 is a reply to message #32424] |
Sat, 25 July 2009 22:42  |
| Eclipse User |
|
|
|
Just out of interest - how are you using AspectJ in a JME world ?
You may want to look into AspectME as well, pretty cool stuff that
allows you to weave JME apps.
Cheers,
Diego
Victor Llorens wrote:
> Thanks for your answres David,
>
> Your are right, amb doing those steps. Even more, if I remove AspectJ
> from the classpath project does not compile.
>
> Dunno if it is fault of the preferifyer step or the package builder one.
> Maybe this is the main problem.
> Do you know if MTJ fills an error log?
>
>> What do you mean with the paragraph bellow ??
>
>>> By the way, in the builders preference page, I can see how the number
>>> of "package builder"(s) checkboxs is increasing as I make changes in
>>> the configuration.
>
> It's something derived after I got the errors. It's like every time I
> reproduce the error, a new package builder appears in the list. And I
> think it's not normal behaviour.
>
> Thanks,
> Víctor LLorens
>
>
>
|
|
|
| Re: Build state machine has not been initialized [message #574807 is a reply to message #32286] |
Mon, 13 July 2009 20:06 |
| Eclipse User |
|
|
|
Hi Victor,
Please make sure you are adding the aspectJ library correctly to your
project. Please take some time to read the following page
( http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse .mtj.doc.user/html/gettingstarted/gettingstarted.html).
Hope it helps you solve your issue.
Regards,
David Marques
Victor Llorens wrote:
> Hi all,
> I'm in a project with AspectJ (AJDT 2.0) + MTJ 1.0 (Pulsar), trying to do
> some stuff with J2ME.
> The configuration of the Eclipse's is the following:
> Aspectj project enabled.
> Put Aspects in classpath when being asked.
> Preverification active, packaging unactive.
> There are no errors in java code. And with this conf, the virtual machine
> can't locate aspects classes when try tu run/debug my app in the emulator.
> In mtj 0.9 I had to put aspectjrt library in the aspect inpath. But if I
> do so with mtj 1.0 I got the error "build state machine has not been
> initialized".
> I have rolled back to mtj 0.9.1 :( .
> Somebody knows about this error? How to solve it? I'm wrong with the
> configuration?
> Thanks in advance,
> Victor Llorens
|
|
|
| Re: Build state machine has not been initialized [message #574827 is a reply to message #32321] |
Tue, 14 July 2009 11:36 |
| Eclipse User |
|
|
|
Yep, this tutorial is a great one. But it's just to create and configure
the MIDLET environment.
If I remove aspectj functionality the project runs well on emulator, even
in the phone. But without aspects.
I've seen another person talking about this 'spamming' message of the
builder.
It's just like MTJ 1.0 is not friendly with ajdt.
By the way, in the builders preference page, I can see how the number of
"package builder"(s) checkboxs is increasing as I make changes in the
configuration.
Seems that this builder is not ok. I really need a response to the main
problem, meanwhile I will continue investigating.
Thanks a lot,
Victor Llorens
|
|
|
| Re: Build state machine has not been initialized [message #574844 is a reply to message #32357] |
Tue, 14 July 2009 12:48 |
| Eclipse User |
|
|
|
Hello Again Victor,
I am getting little lost here! Your main problem is that you are trying
to add aspectJ to your Java ME application right ??
If so then i suppose you are adding the libraries to the application build
path and exporting the library in order to add the library class files
into the mobile application package right !?
Are you saying you are having problems while packaging the application !?
What do you mean with the paragraph bellow ??
> By the way, in the builders preference page, I can see how the number of
> "package builder"(s) checkboxs is increasing as I make changes in the
> configuration.
|
|
|
| Re: Build state machine has not been initialized [message #574858 is a reply to message #32392] |
Wed, 15 July 2009 03:16 |
| Eclipse User |
|
|
|
Thanks for your answres David,
Your are right, amb doing those steps. Even more, if I remove AspectJ from
the classpath project does not compile.
Dunno if it is fault of the preferifyer step or the package builder one.
Maybe this is the main problem.
Do you know if MTJ fills an error log?
> What do you mean with the paragraph bellow ??
>> By the way, in the builders preference page, I can see how the number of
>> "package builder"(s) checkboxs is increasing as I make changes in the
>> configuration.
It's something derived after I got the errors. It's like every time I
reproduce the error, a new package builder appears in the list. And I
think it's not normal behaviour.
Thanks,
Víctor LLorens
|
|
|
|
| Re: Build state machine has not been initialized [message #575424 is a reply to message #32424] |
Sat, 25 July 2009 22:42 |
| Eclipse User |
|
|
|
Just out of interest - how are you using AspectJ in a JME world ?
You may want to look into AspectME as well, pretty cool stuff that
allows you to weave JME apps.
Cheers,
Diego
Victor Llorens wrote:
> Thanks for your answres David,
>
> Your are right, amb doing those steps. Even more, if I remove AspectJ
> from the classpath project does not compile.
>
> Dunno if it is fault of the preferifyer step or the package builder one.
> Maybe this is the main problem.
> Do you know if MTJ fills an error log?
>
>> What do you mean with the paragraph bellow ??
>
>>> By the way, in the builders preference page, I can see how the number
>>> of "package builder"(s) checkboxs is increasing as I make changes in
>>> the configuration.
>
> It's something derived after I got the errors. It's like every time I
> reproduce the error, a new package builder appears in the list. And I
> think it's not normal behaviour.
>
> Thanks,
> Víctor LLorens
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04647 seconds
Home