1 / 68

Don Brutzman brutzman@nps 26 December 2007

Netbeans 6.0 version control configuration for AUV Workbench & various XMSF projects TODO : check changes in all Netbeans 5 screens. Don Brutzman brutzman@nps.edu 26 December 2007. Netbeans setup 1. Install latest Java 1.6, Netbeans 6.0

oliver
Download Presentation

Don Brutzman brutzman@nps 26 December 2007

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Netbeans 6.0 version control configurationfor AUV Workbench & various XMSF projectsTODO: check changes in all Netbeans 5 screens Don Brutzman brutzman@nps.edu 26 December 2007

  2. Netbeans setup 1 • Install latest Java 1.6, Netbeans 6.0 • Bundled version works well: http://www.netbeans.org • http://java.sun.com or http://java.sun.com/j2se/1.6.0/download.jsp • Further Java setup checks • Ensure no other versions of Java or Netbeans installed • Ensure JAVA_HOME properly set • Netbeans Tools -> Update Center for updates

  3. Netbeans setup 2 • Netbeans – Tools – Update Center • Update all modules for latest greatest

  4. Netbeans cvs project setup 3 • Don’t enable old version control • Enable updated version control

  5. Suggested target locations C:\auv\AuvWorkbench C:\CvsProjects\DisJavaProject C:\CvsProjects\DisXmlProject C:\CvsProjects\SavageStudioProject C:\CvsProjects\ViskitProject C:\CvsProjects\XsbcProject CVS module names AuvWorkbench disjava disxml SavageStudio Viskit+Diskit xsbc Netbeans cvs project setup 4 • Create meaningful target directories • Having common parent directory is helpful • Select or enter module name • during initial CVS checkout

  6. Netbeans cvs project setup 5 • Basic setup procedure simpler than 4.0 • No more ‘Versioning’ panel to fool with  • Simple two-part process • Check out via cvs • Click to Create Project • Avoid importing 4.1 settings, they may fail • Follow-on directions show type-in values blocked out in red • Other values are usually found automatically

  7. Netbeans cvs project setup 6 • Server-side authentication keys must be cached prior to initial cvs checkout • Use the PuTTy tool to secure-shell (ssh) into the cvs server • Example: xmsf.cvs.sourceforge.net • Log in using checkout account name • Screen snapshots follow

  8. PuTTY initialization of ssh key Necessary step for software developers prior to cvs checkout 1 3 2 4

  9. Additional developers setup 1 • Developers making and committing source changes into one of the cvs archives need to first install putty tools, then get account • Putty security tools: • http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html • Requesting a developer account: • Don McGregor (xmsf) mcgredo@nps.navy.mil • Arnie Buss (Simkit) abuss@nps.navy.mil

  10. Additional developers setup 2 • wincvs is separate alternative, usually not needed • http://www.wincvs.org/download.html

  11. Configure Netbeans defaults to support greater memory • C:\Program Files\netbeans-5.0\etc • Edit file netbeans.conf • netbeans_default_options="-J-Xms32m -J-Xmx128m (etc.) changed to • netbeans_default_options="-J-Xms32m -J-Xmx1024m

  12. New Netbeans 5.0 cvs features • Top-level CVS menu • Can update all projects at once • Can show CVS committers by name and versions by number in text editor • Features presentation: http://www.javalobby.org/eps/netbeans5

  13. Note committer names, line by line

  14. Further resources • Tutorial by Arnie Buss on Netbeans use provides further background and details http://diana.cs.nps.navy.mil/~ahbuss/CVSNetbeans • Don McGregor's slideset guides to Concurrent Version System (CVS), Using CVS with SSH Tunnels and Ant available online • XMSF Bugtracker http://xchat.movesinstitute.org/bugzilla

  15. cvs checkout + project setup • configuration troubleshooting

  16. project index AuvWorkbench project https://www.movesinstitute.org/xmsf/xmsf.html#Projects-AUV

  17. CVS Root::ext:anonymous@xmsf.cvs.sourceforge.net:/cvsroot/xmsf

  18. Module to checkout: AuvWorkbenchLocal folder: c:\auv

  19. Location: c:\auv\AuvWorkbench

  20. Build and Run Actions are found automatically from build.xml

  21. Source package folder: C:\auv\AuvWorkbench\src

  22. Java sources classpath:c:\auv\AuvWorkbench\launchwb.jar

  23. project index dis-java project

  24. CVS Root::ext:anonymous@xmsf.cvs.sourceforge.net:/cvsroot/xmsf

  25. Module to checkout: disjavaLocal folder: C:\CvsProjects\DisJavaProject

  26. Build and Run Actions are found automatically from build.xml

  27. project index dis-xml project

  28. CVS Root::ext:anonymous@xmsf.cvs.sourceforge.net:/cvsroot/xmsf

  29. Module to checkout: disxmlLocal folder: C:\CvsProjects\DisXmlProject

  30. Location: C:\CvsProjects\DisXmlProject\disxmlProject Name: disxml

  31. Build and Run Actions are found automatically from build.xml

  32. project index SavageStudio project

  33. CVS Root::ext:anonymous@xmsf.cvs.sourceforge.net:/cvsroot/xmsf

  34. Module: SavageStudioLocal Folder: C:\CvsProjects\SavageStudioProject

  35. Location: C:\CvsProjects\SavageStudioProject\SavageStudio

  36. Build and Run Actions are found automatically from build.xml

  37. Source package folders

  38. project index Simkit/Viskit/Diskit/Gridkit Discrete-event simulation (DES)

  39. subversion Root: https://eos.nps.edu/wcm/Viskit/trunk Anonymous access not permitted, POC abuss@nps.edu

  40. accept server signature

  41. browse folders, select trunk for checkout

  42. checkout to local disk directory(same root locations for Viskit, Diskit)

  43. Netbeans checkout in progress..

  44. Following default checkout, run build-run-default-plain

More Related