Package naming conventions and Jar files

All Java classes developed as part of this project MUST be a member of package

         unm.cs351.s05.lastname.p2

or a sub-package of that. In the package name, lastname stands for the designer's last name. E.g., Dr. Lane would make all of his classes members of package unm.cs351.s05.lane.p2 or a sub-package. The designer is free to provide additional sub-packages as necessary.

All handins MUST be in jar files named either lastname_p2m1.jar or lastname_p2m2.jar (as appropriate). Both jar files MUST provide a Main-Class declaration that specifies the default behavior of the jar file when invoked with java -jar. For Milestone 1, the default class MUST be ZurkParser. For Milestone 2 (rollout), the default class MUST be Zurk.