Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » DSDP - Mobile Tools for Java (MTJ) » Eclipse Pulsar - a huge step backward?
Eclipse Pulsar - a huge step backward? [message #516240] Tue, 23 February 2010 10:28 Go to next message
Eclipse UserFriend
Originally posted by: krischik.users.sourceforge.net

Hello

some time ago I "upgraded" to Eclipse Galilio and it's the Pulsar setup
for mobile development. And I have to say: I regret it badly.

I begin to wonder if Pulsar is a huge step backward. Yes Pulsar hat a
few new ideas and it seems to be cleaner framework. But it also seems to
be not quite as stable and has broken backward compatibly badly.

First for me the migration tool has made such a bad job I would have
been better off without. For least I could have made a quick roll-back.

But mostly even after hours of repair work all I get are endless error
message. I give you couple of examples:

------------------------------------------------------------ ------------
Sony Ericsson SDK 2.5.0.3 for the Java(TM) ME
Platform(Emulator)/SonyEricsson_P990_Full_Emu was converted to Sony
Ericsson SDK 2.5.0.6 for the Java(TM) ME
Platform(Emulator)/SonyEricsson_P990_Full_Emu
------------------------------------------------------------ ------------
Nice info - but why repeat if after each compile - just remember it or
tell me how to get rid off it for good.

------------------------------------------------------------ ------------
Errors occurred during the build.
Errors running builder 'Preverification Builder' on project 'Calculator'.
Build state machine has not been initialized.
Build state machine has not been initialized.
------------------------------------------------------------ ------------
Repeated six times and comes with it's own super-duper annoying error
box. And of course useless as there is not indication on how to
initialize the state machine. This is a real dead-lock - I searched the
web and there seem to be no way to initialize the state mashine short of
"del /S .metadata". I did that - it was only a relive for a very short time.

Of course, I would have done:

if (! stateMashine.isInit ())
{
stateMashine.init ();
}

Far more helpful then an silly error message.

------------------------------------------------------------ ------------
C:\work\uiq3\JavaME\Informer\.mtj.tmp\emulation (Zugriff verweigert)
java.io.FileNotFoundException:
C:\work\uiq3\JavaME\Informer\.mtj.tmp\emulation (Zugriff verweigert)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
at
org.eclipse.mtj.internal.core.project.midp.ApplicationDescri ptor.store(Unknown
Source)
at
org.eclipse.mtj.internal.core.packaging.midp.DeployedJADWrit er.writeJad(Unknown
Source)
at
org.eclipse.mtj.internal.core.packaging.midp.DeployedJADWrit er.writeDeployedJAD(Unknown
Source)
at
org.eclipse.mtj.internal.core.build.packaging.PackageBuilder .updatePackage(Unknown
Source)
at
org.eclipse.mtj.internal.core.build.packaging.PackageBuilder .doBuild(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.basicBuildLoop (BuildManager.java:309)
at
org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:341)
at
org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBu ildJob.java:140)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJ ob.java:238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
------------------------------------------------------------ ------------
Of course "C:\work\uiq3\JavaME\Informer\.mtj.tmp\emulation" exists and
is user writeable! What is Pulsar really telling me here?

I guess those problems can be solved by over-gurus or with endless
amount of time - probably involving recreating the whole build and
project system. Juck!

But before I do that: Anybody got experience with one of the two Maven 2
setups for Jave ME developments. Because if I have to redo my build
set-up I rather spend my time moving to Maven.

Martin
--
mailto://krischik@users.sourceforge.net
Ada programming at: http://ada.krischik.com
Re: Eclipse Pulsar - a huge step backward? [message #516329 is a reply to message #516240] Tue, 23 February 2010 15:37 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: krischik.users.sourceforge.net

Martin Krischik schrieb:

> But before I do that: Anybody got experience with one of the two Maven 2
> setups for Jave ME developments. Because if I have to redo my build
> set-up I rather spend my time moving to Maven.

Actually I tried that one myself on a smaller project and indeed the
j2me-maven-plugin (http://pyx4me.com) plus m2eclipse
(http://m2eclipse.sonatype.org) work a dam side better. If I consider
that I sunk 10 times the effort into Pulsar and Mobile Tools for Java
with nothing to show for it I think that Pulsar might be a dead end and
Maven is the way to go.

But then: I already think that Eclipse projects for general Java
development are a dead end and Maven projects are the way to go.

Martin

--
mailto://krischik@users.sourceforge.net
Ada programming at: http://ada.krischik.com
Build with Maven (Was: Eclipse Pulsar - a huge step backward?) [message #516700 is a reply to message #516329] Wed, 24 February 2010 19:43 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: krischik.users.sourceforge.net

Am 23.02.2010, 16:37 Uhr, schrieb Martin Krischik
<krischik@users.sourceforge.net>:

> Martin Krischik schrieb:
>
>> But before I do that: Anybody got experience with one of the two Maven 2
>> setups for Jave ME developments. Because if I have to redo my build
>> set-up I rather spend my time moving to Maven.
>
> Actually I tried that one myself on a smaller project and indeed the
> j2me-maven-plugin (http://pyx4me.com) plus m2eclipse
> (http://m2eclipse.sonatype.org) work a dam side better.

And to add an extra twist: Maven will compile JavaME applications on OS X
- something which never worked before. Mostly because of the missing
preverifier.

Martin

--
Martin Krischik
Re: Build with Maven (Was: Eclipse Pulsar - a huge step backward?) [message #529854 is a reply to message #516700] Tue, 27 April 2010 13:19 Go to previous messageGo to next message
Gustavo de Paula is currently offline Gustavo de PaulaFriend
Messages: 42
Registered: January 2010
Member
hi,
there is bug filed about the build state machine not initialized issue. there is also a workaround that can be used.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=310625

aboud macOs support, this is associated to the SDK not to MTJ itself. MTj does not have any platform dependen feature. if you want to use macOS there are a couple of options that work ok with MTJ such as the Motorola SDK and microemu and mpower player. MTJ also have an option that you can manually configure the preverifier that you want to use. with that you can use any preverifier you want

Smile
gep
Re: Eclipse Pulsar - a huge step backward? [message #579706 is a reply to message #516240] Tue, 23 February 2010 15:37 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: krischik.users.sourceforge.net

Martin Krischik schrieb:

> But before I do that: Anybody got experience with one of the two Maven 2
> setups for Jave ME developments. Because if I have to redo my build
> set-up I rather spend my time moving to Maven.

Actually I tried that one myself on a smaller project and indeed the
j2me-maven-plugin (http://pyx4me.com) plus m2eclipse
(http://m2eclipse.sonatype.org) work a dam side better. If I consider
that I sunk 10 times the effort into Pulsar and Mobile Tools for Java
with nothing to show for it I think that Pulsar might be a dead end and
Maven is the way to go.

But then: I already think that Eclipse projects for general Java
development are a dead end and Maven projects are the way to go.

Martin

--
mailto://krischik@users.sourceforge.net
Ada programming at: http://ada.krischik.com
Build with Maven (Was: Eclipse Pulsar - a huge step backward?) [message #579727 is a reply to message #516329] Wed, 24 February 2010 19:43 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: krischik.users.sourceforge.net

Am 23.02.2010, 16:37 Uhr, schrieb Martin Krischik
<krischik@users.sourceforge.net>:

> Martin Krischik schrieb:
>
>> But before I do that: Anybody got experience with one of the two Maven 2
>> setups for Jave ME developments. Because if I have to redo my build
>> set-up I rather spend my time moving to Maven.
>
> Actually I tried that one myself on a smaller project and indeed the
> j2me-maven-plugin (http://pyx4me.com) plus m2eclipse
> (http://m2eclipse.sonatype.org) work a dam side better.

And to add an extra twist: Maven will compile JavaME applications on OS X
- something which never worked before. Mostly because of the missing
preverifier.

Martin

--
Martin Krischik
Re: Build with Maven (Was: Eclipse Pulsar - a huge step backward?) [message #580056 is a reply to message #516700] Tue, 27 April 2010 13:19 Go to previous message
Gustavo de Paula is currently offline Gustavo de PaulaFriend
Messages: 42
Registered: January 2010
Member
hi,
there is bug filed about the build state machine not initialized issue. there is also a workaround that can be used.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=310625

aboud macOs support, this is associated to the SDK not to MTJ itself. MTj does not have any platform dependen feature. if you want to use macOS there are a couple of options that work ok with MTJ such as the Motorola SDK and microemu and mpower player. MTJ also have an option that you can manually configure the preverifier that you want to use. with that you can use any preverifier you want

:)
gep
Previous Topic:MJT and Java ME SDK 3.0
Next Topic:Unable to import devices from j2me sdk3
Goto Forum:
  


Current Time: Tue Dec 23 01:37:51 GMT 2014

Powered by FUDForum. Page generated in 0.02044 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software