Ah; I see what you're tring to do.  Did you change the NodeVR.java in
/citypub/www/city/datadev, or somewhere else?  datadev is the place you want
to do your work if you want to make changes to the old production site.  The
good news there is that this stuff is maintained in a separate CVS module
(and has remained basically unchanged), so there shouldn't be any
compatibility problems related to the development I did for data2.  I think
the reason "make release" did nothing for you is that you're doing from it
the wrong place.  You need to be working from /citypub/www/city/.

Here's an enumeration of the steps you need to take:

1.  Fix NodeVR in the /citypub/www/city/datadev source tree.
2.  cd to /citypub/www/city/
2.  Run "make" to build the test site (which is deployed in
/citypub/www/city/datadev).
3.  Test it out.
4.  When satisfied, run "make release" (also from /citypub/www/city).
5.  Check your changes in; they should not conflict with data2 (but you will
have to re-do the work there when the time comes).

Step 4. should push your changes to the release site.

-z

PS:  Sorry about the confusion.

> -----Original Message-----
> From: Seth Teller [mailto:teller@lcs.mit.edu]
> Sent: Thursday, January 23, 2003 2:16 PM
> To: Zachary Bodnar
> Subject: Re: citydata questions
> 
> 
> 
> zach,
> 
> ok, this is indeed more complex than i thought.  
> 
> for now, i just wish to fix the compass bug.  i went to the
> top of /data -- the old production site -- and did make release,
> and that had no effect.  [i couldn't follow your instructions,
> literally, since it seems that you were telling me to fix it
> in the new (as yet undeployed) code base and redeploy -- this
> seems too aggressive of an upgrade.]
> 
> anyway, please clarify what i need to do in order to get 
> only a minimal upgrade (bug fix) to the site in /data.
> 
> as for future dev't -- i am trying to recruit someone
> to carry the torch on this; once s/he's on board i 
> will try to fold all of this into the instructions.
> 
> seth.
> 
> Zachary Bodnar wrote:
> > 
> > yeah... my email forwarding seems to be in a state of 
> turmoil.  endeca is
> > fine; use that.
> > 
> > I've looked into this:  First let's make sure we're talking 
> about the same
> > versions of the project.  There is the old version of the 
> site, which just
> > used plain html and perl, and then there was the advanced 
> version which used
> > Servlets and the navigation stuff that I wrote for my thesis.  These
> > actually live in two different modules of the CVS 
> repository (it might've
> > been better to branch, in retrospect...), so there are 
> actually two copies
> > of the applets.  I suspect you're comparing the new code to 
> the old stuff
> > that is in the old production site (see below).
> > 
> > The new stuff lives in $CVSROOT/data2.  In that directory 
> are some notes
> > about how to build the site and starting points for 
> continuing development
> > on it in a file called citydata.readme.  Check this out and 
> read through it.
> > Looking at these notes I was reminded that although we 
> setup production and
> > development environments for the original site, there is 
> only one deployment
> > of the new site, so running make will deploy all the 
> changes there; there is
> > no implementation of "make release" for the new site.  
> Also, it looks like
> > clicking on "browse our ... data online!" from the main 
> city.lcs.mit.edu
> > site sends you to the OLD production site.
> > 
> > What this breaks down to, in terms of where the stuff is 
> actually deployd is
> > this:
> > 
> > /citypub/www/city/data -> old production site (what is 
> linked from the main
> > city site)


This explanation seems to make sense to me:

http://clue.denver.co.us/pipermail/clue-tech/2001-November/002163.html

Make sure your browser and your java class files are compatible.

1) All of the code uses java 1.1, so make sure you haven't added any Java
>=2 in there (I'm pretty sure you didnt').
2) Make sure your browser is Java 1.1 compatible (netscape on the  SGIs is
an excellent baseline test, since it uses a relatively archaic java 1.1 VM.
If it works there, it should work everywhere).
4) Check whether your compiler is too new.  I think they try to back-compat
everything, but may occasionally remove deprecated features.
5) Some dependencies may be screwed up.  You might want ot try a clean
rebuild (of the dev site).

> -----Original Message-----
> From: Seth Teller [mailto:teller@lcs.mit.edu]
> Sent: Thursday, January 23, 2003 4:20 PM
> To: Zachary Bodnar
> Subject: Re: citydata questions
> 
> 
> 
> ok, i remade, then pointed the browser to citydev.
> 
> i get "bad major version number" in the java status bar
> of my browser.
> 
> why is that ?
>