annuello wrote: »
Hmmm... What a "fun" time for me to be getting into Duet development. I'm having a similar issue, but with a different class. Works on fw v3, but throws the NoClassDefFoundError error on fw v4.
So as a newbie in Duet dev, what is the best way for me to handle this? I'm writing a module which I expect will need to run on both v3 and v4 firmware editions. Surely I don't have to make and distribute two versions of the module? I mean, I can cope with that if it is the only way, but.... yuck!
Where can I find out what has/has-not been dropped in v4? It seems pointless designing for v3 if v4 drops my bundle dependencies. And designing for v4 without knowing what classes are available/relocated, well that is just guess-work. My biggest concern is that if I build on v3 (since I can see what is available) my dependencies may very well be gone in v4.
sonny wrote: »
FWIW Roger, at this point I haven't been able to get a date out of AMX as to when a 4.x Java development update will happen. As far as I can tell, the bundle AMX is using is Knoplerfish 2.3.something. OSGi is 4.1.13, Java 1.4.2. I was really hoping we'd be farther along on Java version at this point.
One thought regarding microedition.io, you could try adding the source for the classes you need to your module. I've done this with several classes that weren't a part of j2me.jar through the years.
I've got several modules with microedition.io as well as Jetty, so I decided not to move to v4 at this time. I have used AMX with Java to do some equipment monitoring systems in the past, mainly because of the hardware options, but at this point I'm moving all that to Linux.