Document update suggestion.
Keeping in mind the documents are implied as step by step instructions.
The instruction |cvs update -dP could get complicated for some
developers due to
|
|missing perquisites steps on page
http://tomcat.apache.org/tomcat-9.0-doc/appdev/source.html|
|The two steps I can remember I did at the time was to create a
directory "CVSROOT" at ~/cvs/CVSROOT
|
|then point to that directory as the "cvs application" home directory
with the command|
||
|$ *cvs -d /nfs/roc/home/cvs command*|
||
|I actually went to this page
https://www.eoas.ubc.ca/research/moc2/cvstutorial/setting.html
|
|to complete the setup because your documents are incomplete.|
|
|
|I also think I had a smoother ride of the setup because I was using a
*.nix {ubuntu} so the VI/VIM editors,|
|which are built in the Operating System launch automatically without
issue with cvs.
|
|I also noticed on another mailing list some people, who even work as a
pair still couldn't get "up and running"
|
|with the supplied maven archetype examples. Due to the fact mvn command
line |||argument(s) ||||{ javafx:run || jetty:run ] |was not mentioned .|
|In this case javafx:run need to be set as goals for this particular
IDE. Due to missing setup instruction(s) the time and effort of
archetype can go to waste. These minor missing instructions can be a
major headache in getting a potential developer "up and running".|
|This "up and running" is not just a step but an important *milestone*
especially For experienced developers. This is because after that the
experience developers know from this point on they have taken over
control of the software behaviour.
|
b/r
Zahid
www.backbutton.co.uk
¯\_(ツ)_/¯
I ♡۶ Lynx text browser
recover crashed ms-word .doc with ms-debug.
use file header with filename.
