Yes, I agree that we can get rid of Jmol-HEAD, but we need to modify the
scripts
(I think it's the build.xml of Jmol-web that needs to be modified).
Be careful, the "HEAD" you see in the CVS repository has nothing to do
with the name "Jmol-HEAD".
If we replace Jmol-HEAD with Jmol, the only thing to do in Eclipse is:
- rename the project Jmol-HEAD to Jmol
OR
- delete the project Jmol-HEAD and checkout Jmol again as Jmol
Bob Hanson wrote:
Nico, are you in agreement with Miguel that there is no need for
labeling the project "Jmol-HEAD" and
instead just go with "Jmol"? I see now that HEAD is the first entry in
my CVS repository view. I also see (I think) that there are no
additional branches. Have I got that right? And then the "Versions"
set must hold the actual released 10.00.xx version. Don't worry -- I
won't touch that. I take it that is Miguel's baby.
I've started over. Now I have
c:\jmol-dev\workspace\Jmol
c:\jmol-dev\workspace\Jmol-web
I've run both the applet and the app now from Eclipse. This is fun!
I agree with you, Nico, Eclipse is excellent. Far far easier than I
imagined.
I'm mystified how it was able to handle extssh without my uploading my
ssh public key manually the way that was necessary in WinCVS/WinSCP.
Of course, I haven't tried to upload anything, either!
That's part of why I think Eclipse is the best way to go for "novice"
developers with Jmol.
There's not much to setup to get it fully operationnal :)
Looks like all I need to do now is link in javac, and I'll be up and
running.
So if I were to add a file to one of these directories from outside
Eclipse -- a data file, for example -- would that be recognized in the
project and uploaded when I went to commit the next time?
If you had files to the directories from outside Eclipse, you have to
tell Eclipse to update the directories (select the project and press F5).
You will then see the new file with a question mark and a '>' under
Eclipse (question mark is for files not currently under CVS, '>' is for
modified files).
To add it to CVS, right click on it and select Team / Add to Version
Control.
The next time you do a commit, the new file will be committed.
Also, how does the locking work -- I don't want to accidentally set
locks.
And, what ended up happening with that recent lock? Why was it set?
How did you get it unlocked?
You don't have to worry about locks usually:
It is automatically set and then removed when you commit or update to
prevent two people to modify the same file simultaneously.
The recent lock happened because the cvs server crashed when I committed
a file (I don't knwo why), so the lock stayed.
I created a bug report for the sourceforge team and they manually
removed the lock.
Nico
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Jmol-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-developers
