[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [stellation-res] Repository Contents - Status Update
|
On Friday, September 12, 2003, at 01:10 AM, Jim Wright - IBM Research
wrote:
Per my email of Sept 10, I've been working on bringing
the repository contents fully up to date.
Briefly: I ran into some technical glitches, now
resolved, but have not been able to finalize everything
by today as hoped. I should be able to complete the
work when I return on Tuesday (I'm away Friday through
Monday for a family obligation).
The biggest issue was my flirtation with Java 1.4.1,
which I installed (on XP and Linux) last week. While
things initially seemed to work (on XP), I've concluded
that the Eclipse R3.0 stream and the Java2 1.4.1 JRE do
not play nicely together. (Classpaths are not built
when projects are imported; Eclipse malfunctions in
assorted ways ... not pretty. I've added comments to
related Bugzilla entries for Eclipse Platform).
I also upgraded from RH Linux 7.3 to RH9 (and from
Win2K to Win XP) last week, requiring a full reinstall
of both systems; today I found out that a few things
were missed along the way...
As things stand, I have now rebuilt everything locally
(Eclipse GUI, Stellation core, VSF, Stim, the works)
with apparent success, and have connected to the
stellation.eclipse.org repository. I've had to modify
build-stell.xml to avoid an unfortunate issue w.r.t.
/usr/local/bin on Linux (which is now used by various
other apps, so simply trashing it is _very_ rude).
Install docs still need to be updated, omitted files
checked in, extraneous files deleted .... but it
should be relatively straightforward, once I'm back in
NY again.
Not to be overly rude, but.... What on *earth* are you smoking?
Where do we *trash* /usr/local/bin? Where on earth did you get the
idea that /usr/local/bin is something *new*? (The use of /usr/local/bin
for local binaries dates back to roughly *1997*. To my knowledge,
there has never been a distribution of linux that doesn't include
binaries in /usr/local/bin.
And if our build scripts had been blowing away /usr/local/bin, then I
would
regularly have watched my machine die - because I run XFCE 4, installed
in /usr/local, binaries in /usr/local/bin - so my entire desktop would
have been
obliterated.
Also, the Eclipse R3.0 stream supposedly *only* works on 1.4 level
JVMs. I double checked, and my linux box is running IBM Java 1.4.1,
Eclipse R3M3, with absolutely no problems. So it's not strictly
a JVM issue - there's something environmental going on. Are
you sure that you don't have any lingering metadata? (The only
classpath problems that I've experienced were related to, I think,
.project files that had hardwired references to a 1.3 JVM.)
-Mark
Mark Craig Chu-Carroll, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM Research
*** http://stellation.eclipse.org
*** Work: mcc@xxxxxxxxxxxxxx/Home: markcc@xxxxxxx
