waht about java

i saw that jnode is using the gnu classpath at lees is what i'm watching on the left side
and the incompatibility of these with sun java

why not use the sun java now is open ????

if the license is a problem
why not use then the Apache Harmony that is more compatible with sun java up to 95%

a dont now if there is a problem with the license of apache

sorry by my english

I fully agree with

I fully agree with FabienD's message below, but want to do some other comment on it:
Harmonys licences is ok for JNode (just like sun java and gnu classpath), but we couldn't use the VM itself, because it's C/C++ code (same applies to sun). Besides that, afaik Harmony is not 95% but at most 75% jdk5 complete. Gnu classpath has around 99,xxx%?! What JNode needs is a classlib, with as much stuff written in Java as possible and that's gnu classpath atm and probably in the future too.

About sun's code, it's still not released, so best to wait for the source and decide then. Atm it's very difficult to estimate the work that would be needed to switch the classlib.

Anyway I'm wondering a bit about it. Is anyone not content with gnu classpath? They did a really great work and helped JNode a lot. Further on, now that they nearly completed their work and we have a good working VM interface between classpath and JNode, why switch at all?

Peter

my opinion

1. About the truth of Harmony, see Harmony's website: http://harmony.apache.org/roadmap.html
DONE Nov 2006 : 95% of Java SE 5 class library coverage
...
Q2 2007 : TCK certification of Harmony completed
Q2 2007 : Apache Harmony SE 5 JDK and JRE released
Q4 2007 : Apache Harmony SE 6 JDK and JRE released
Q? 2008 : Apache Harmony SE 7 JDK and JRE released.

2. GNU Classpath is great, but is not very friendly to Windows.
I'm *not* a trivial java guy, and I used to try to get Classpath worked in my windows, but I'm failed. Classpath is just "classpath", and not include a VM. However, the main VMs binding Classpath is not very friendly to Windows yet. They do not offer windosw binary.For sources, they like to use the make, not ant. They aslo only support Cywin, not VC(MS VC Express is free now). They are very not elegant and even ugly for *Java* dev under the *windows*. I know, most of open developers are using Linux, but we should regard developers under windows. And the thinking of Java is platform-independent, why we mess platform-denpendent things into it?

3. I agreen with FabienD partly.
In my opinion, we should not just be satisfied with JNode's working. We should make jnode elegant and decent. I believe we should revisit the core of jnode. There are several problems seem not resolved in Jnode, I think. But, working is better than talking. I'll just discuss them after my finish the study of jnode.

Hi surfeit, seems I missed

Hi surfeit,

seems I missed much development of harmony Smiling I wasn't aware they are so far allready. Also your point about Win+classpath might be right, I don't know that. But why is that needed at all for JNode?
(gnu classpath code in JNode gets compiled with ant)

At least I test all my stuff with normal sun jdk outside JNode and with classpath only in JNode. So could you elaborate why you/we need the same VM+classlib inside and outside JNode?

Again, not that I'm against a switch, but I don't see the reason for it. Especially since we have more serious problems than missing jdk compliance (like you and FabienD said too).

Peter

Peter, You are right:)

Our developer is too rare to do many things concurrently:) I'm doing some GUI tries in recent days, but I find some thinking of jnode plugin is not very satisfying to me. One thing is about component developing of jnode. So, I hope jnode could be more componentized^_^
But I failed to see that we've had many things to do:)
I hope do some studying of the probability of jnode-osgi(Equinox) fusion(In my view, now the plugin framwork of jnode is more similar to Eclipse Equinox than osgi). But I'm not sure there will be a result:)

I worked (a bit) on jnode-osgi fusion !

You should know that I worked (a bit) on jnode-osgi fusion.
So, we should meet on irc to discuss about that.

From what I have seen, that's not as easy as you think. But I hope you understood all what has to be done and so the work is easier than what I thought Smiling

Fabien

my blog (in english and french)

I agree with you

Sun' java GPLed implementation has a "Classpath Exceptation" License.(I'm not sure it is ok for jnode. who know the detail?) So, I think Apache Harmony seem the better choice. And the Harmony has a modular archeture. It will allow to customize the JNode easier.(Where is the mini-jnode?) The Harmony is more osgi-like. That is a directon of JNode. And the Harmony is full-featured and targeted for all platform, GNU Classpath is just a class lib(?seem heavy use linux thinking?such as makefile, not ant). So it should be easier to debug application in other platform before JNode' mature using Apache Harmony.
In a whole, I also sugguest to considering to use Harmony in JNode.

some details

The "GPL with Classpath Exception" License is the Classpath license, which is compatible with JNode license (LGPL).

sun's jdk has/will have the same license (GPL with Classpath Exception). So, no problem with that from license point of view. But from technical point of view, I think that would be difficult.

For building JNode, we don't need linux (ou can use windows if you want).

About Harmony, I think they are late compared to GNU Classpath implementation : that will be a lot of work and regression for JNode (we have more important things to do on JNode).

I don't mean we shouldn't use Harmony or sun's jdk. I just mean that's not our priority. Anyway, about sun's jdk, GNU Classpath may decide to integrate some part of it if they feel the need of doing so.

Fabien

my blog (in english and french)