Eclipse 3.0M4 came out today, but there is no QNX build. What’s up ?
Rennie
Rumors are, there are problems for this combo, which are being worked out…
“Rennie Allen” <rallen@csical.com> wrote in message
news:bmh5ok$l63$1@inn.qnx.com…
Eclipse 3.0M4 came out today, but there is no QNX build. What’s up ?
Rennie
Igor Kovalenko wrote:
Rumors are, there are problems for this combo, which are being worked out…
Hmmm, you’d think that QSS would do a better job of managing this. Eclipse
is a very high profile project (millions of users), seeing QNX dropped from
the list without explanation is very bad publicity.
Rennie Allen <rallen@csical.com> wrote:
Eclipse 3.0M4 came out today, but there is no QNX build. What’s up ?
It’s a pretty simple situation. The class libraries supplied with j9 are
not at a JDK 1.4 level. Offically they are not even 1.3, but they did have
most of the 1.3 API in place. There are several options being sorted out,
but until they are sorted out and publically avaliable, there will not be
any QNX builds of the 3.0 stream of Eclipse past M3.
This isn’t a surprise either BTW, it is something that we have known Eclipse
was going to do for a number of months.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Chris McKillop wrote:
Rennie Allen <> rallen@csical.com> > wrote:
It’s a pretty simple situation. The class libraries supplied with j9 are
not at a JDK 1.4 level. Offically they are not even 1.3, but they did have
most of the 1.3 API in place. There are several options being sorted out,
but until they are sorted out and publically avaliable, there will not be
any QNX builds of the 3.0 stream of Eclipse past M3.
This is disappointing. I don’t suppose there is any publicly available
information about when this might be resolved is there ? Before 3.0 release ?
This isn’t a surprise either BTW, it is something that we have known Eclipse
was going to do for a number of months.
I’m sure it wasn’t a surprise for you, but I didn’t see any public announcement
regarding this.
It’s a pretty simple situation. The class libraries supplied with j9 are
not at a JDK 1.4 level. Offically they are not even 1.3, but they did have
most of the 1.3 API in place. There are several options being sorted out,
but until they are sorted out and publically avaliable, there will not be
any QNX builds of the 3.0 stream of Eclipse past M3.This is disappointing. I don’t suppose there is any publicly available
information about when this might be resolved is there ? Before 3.0 release ?
I would hope the issue would be resolved before 3.0 release. That is more then
6 months away still.
I’m sure it wasn’t a surprise for you, but I didn’t see any public announcement
regarding this.
Why would there be? It’s only a milestone build.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Is QSSL going to release a new version of Momentics before version 3.0,
which is 6 months away? Which version and how soon is it?
“Chris McKillop” <cdm@qnx.com> wrote in message
news:bmhqa6$lj0$1@nntp.qnx.com…
It’s a pretty simple situation. The class libraries supplied with j9
are
not at a JDK 1.4 level. Offically they are not even 1.3, but they did
have
most of the 1.3 API in place. There are several options being sorted
out,
but until they are sorted out and publically avaliable, there will not
be
any QNX builds of the 3.0 stream of Eclipse past M3.This is disappointing. I don’t suppose there is any publicly available
information about when this might be resolved is there ? Before 3.0
release ?
I would hope the issue would be resolved before 3.0 release. That is more
then
6 months away still.
I’m sure it wasn’t a surprise for you, but I didn’t see any public
announcement
regarding this.
Why would there be? It’s only a milestone build.chris
–
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Johannes <Jsukamtoh@infolink.co.id> wrote:
Is QSSL going to release a new version of Momentics before version 3.0,
which is 6 months away? Which version and how soon is it?
Information of that nature is best obtained from your sales rep. However,
there will be another release of our product before we move to Eclipse 3.0.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Chris McKillop wrote:
It’s a pretty simple situation. The class libraries supplied with j9 are
not at a JDK 1.4 level. Offically they are not even 1.3, but they did have
most of the 1.3 API in place. There are several options being sorted out,
but until they are sorted out and publically avaliable, there will not be
any QNX builds of the 3.0 stream of Eclipse past M3.This is disappointing. I don’t suppose there is any publicly available
information about when this might be resolved is there ? Before 3.0 release ?
I would hope the issue would be resolved before 3.0 release. That is more then
6 months away still.
It would be easier to implement in 6 monthes the mainstream Java VM from
SUN and its AWT 
The J9 stuff seems to be the false track …
Armin
It would be easier to implement in 6 monthes the mainstream Java VM from
SUN and its AWT >
Feel free Armin! If you read Sun’s licenses you will see that QSS
cannot do this and release a commerical product using it, I am not sure
we could even release a non-commerical product with the binaries produced.
The AWT stuff isn’t needed since Eclipse doesn’t use AWT/Swing at all.
The J9 stuff seems to be the false track …
I don’t think so. It isn’t the vm side that is the trouble right now, it
is purely the classlibs.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
“Chris McKillop” <cdm@qnx.com> wrote in message
news:bn6vu9$rkm$1@nntp.qnx.com…
It would be easier to implement in 6 monthes the mainstream Java VM from
SUN and its AWT >
Feel free Armin! >
cannot do this and release a commerical product using it, I am not sure
we could even release a non-commerical product with the binaries produced.
The AWT stuff isn’t needed since Eclipse doesn’t use AWT/Swing at all.
The J9 stuff seems to be the false track …
I don’t think so. It isn’t the vm side that is the trouble right now, it
is purely the classlibs.
That might be so… but if you look at the list of supported platforms, QNX
is the only one to use non-Sun Java implementation and the only one to have
this problem. Even if the VM is fine, lagging classlibs make it less than
useful. If IBM can’t keep up updating classlibs to whatever current commonly
used feature set it is, then you are stuck with this problem and this is not
the last time you have it.
– igor