1
edit
Changes
→Challenges
:: build the model: go to ws/core/build/ run <code> ant </code> or <code> ant -f build_JUnitTest.xml</code>
:: from command line: go to ws/out/core/ run <code> java junit.textui.TestRunner nexj.core.AllTests</code> (getting error IOExcpetion) so we just ran one test file <code> java junit.textui.TestRunner nexj.core.util.MathUtilTest</code> (We did some changes to <code> core/test/nexj/core/util</code> to practice with it) Or we can run the ant target for test: <code> ant -f build_JUnitTest.xml test </code>
*7- Bugs after implementation at NexJ
: Working with remote repository; getting tip and log from remote repository is not as simple as moving to local repo and get all the information we need.
: NexJ Internal repo has several branches, and when cloning and pulling, we just needed to mention it as a default branch, to not to confuse revision numbers and latest changesets.
: Since the integer part of the revision numbers will keep changing from computer to computer, it was preferred to use the hex part (GUID).
: So, the first big change was adding this command to get the list of latest changesets up to the tip:
:: hg log ${IntDir} -r ${PrevRev}: -b default --template '{node}\n'</code>
: This number will also be added to the commit summary while importing the patch from Internal repo
