Fixes issue #116: org.testng.internal.BaseTestMethod does respect general contract of Comparable
Merge pull request #488 from triceo/master

Fixes issue #116: org.testng.internal.BaseTestMethod does respect genera...
Preparing for release
[maven-release-plugin] prepare release testng-6.8.8
[maven-release-plugin] prepare for next development iteration
Added .ant-targets* to .gitignore, so that target caching does not show as a change.
Updated GitHub project url in README to be 'https' instead of outdated 'http'.

Note that, at the time of this commit, GitHub's policy is to have https only
connections; thus this won't have an effect on which protocol a browser following
this link will actually use.
Updated the snakeyaml version in build.properties to match what ivy retrieves.

The snakeyaml file listed in build.properties for the property 'yaml.jar'
was 'snakeyaml-1.6.jar'. However, ivy retrieves 'snakeyaml-1.12.jar' as a
dependency. The version mismatch was causing the build to fail.
update yaml.jar version in build.properties
Fixed dependencies for 4 targets in build.xml

The targets 'tests', 'test-ant', and 'javadocs' all fail without running the
target 'build' first, since they rely on the testng.jar to run. The target
'build' has been added as a dependency to each of these.

The target 'tests' had previously listed 'compile' as a dependency, but this
has been removed since 'build' covers this already.

Another target, 'create-jar', requires the directory target/classes in order
not to fail, and requires the testng classes to make a meaningful jar. It works
properly once the target 'compile' has been run, so 'compile' is now added to
its dependency list.
Merge pull request #493 from themainfunction/master

A few misc bug fixes to make the build work properly
Use LinkedHashMap so that the topological sort will process the nodes in the same order of collecting
Merge pull request #497 from Dao007forever/master

Use LinkedHashMap so that the topological sort will process the nodes in the same order.
Fixed TOC anchor collisions in documentation-main.html

The table of contents' section links are generated from
anchors of class 'section. There were two collisions of
the anchor names, where two sections shared the same
anchor name:

Sections 'Test methods' and 'Test groups' both used the
	anchor name 'test-groups'
Sections 'Parallel suites' and 'Parallel tests, methods,
	and groups' used the anchor name 'parallel-tests'

Now, these are fixed, with anchor names that match the
section names, and the TOC links work properly.

The anchors for the table of contents are specified by the
name attribute.
Fixed section heading tags (<h3>, <h4>, <h5>) so they are consistent

Sections and subsection headers were inconsistent in their usage
of html heading tags.

The majority of section headings use the following tags based on
their indent attribute:

indent="." or blank =>  <h3>
indent=".."         =>  <h4>
indent="..."        =>  <h5>

However, some of the "..." level tags used <p><em></em></p> or even
<h3> some times. There were inconsistencies like this in a few places.

Now, all of the section headings conform to the above scheme.
Standardized section heading HTML format for easier reading/maintenance.

The HTML for the section headings varied between headings. Sometimes
the <h> tags were on surrounding lines, sometimes they wrapped the
content on a single line, and sometimes they were at the end of the
previous line of content. This made for difficult reading; it also made
changes difficult.

Now, all section heading <h> tags wrap the content on a single line,
in the following format:

<hx><a ...>content</a></hx>

so that they are easy to work with.

NOTE: I'm aware that this may not be compliant with some style guides,
and also that everybody has different preferences. I'm not trying to
enforce my particular preference over anyone else's; I picked this
format simply because A) section heading lines are generally short
enough to fit in screen-width even with <h> tags, and B) many of the
section headings were this way to begin with.
Updated version to be tested to 6.8.9-SNAPSHOT, in pom-test.xml.
testng-496 org.testng.junit.JUnit4TestRunner handles testAssumptionFailure as a failure but it should be ignored
Report test as skip.
Also report as skip from #testFailure with AssumptionViolatedException as failure exception
Remove unnecessary super calls. (RunListener is special not-implementation class)
Fix bug when test with assumption failure reported also as passed.
Add test for this case.
Merge pull request #503 from VladRassokhin/fix-testng-496

Fix for #496
Merge pull request #498 from themainfunction/master

Fixes to documentation-main.html, so that section headings work and look the same.