ArraySequence: Unix newlines
Issue #186: ArraySequence: Add constructor with a length parameter to specify how many of the elements of the backing array are actually part of the sequence
Change build so that JVM-specific tests are in their own source directory, add a test for the JVM runtime version of ArraySequence
Generating junit reports seems to break atm, so disable for now
Issue #186:

* ArraySequence: Make public constructors copy the passed array by default, trusted callers can use a $hidden static method to create an ArraySequence backed by a given array

* segment() not longer deep copies and span()
only does when the order is reversed

* Always use Object[], and not Element[]

* SequenceBuilder and SequenceAppender: Rewrite to avoid using java.util.List, managing their own array instead. This saves an additional array copy.

* When appendAll() is called with an ArraySequence argument allow ourselves to do a System.arrayCopy() of the elements, as a more efficient alternative to Iterating the sequence
Issue #95: Move ArraySequence from com.redhat.ceylon.compiler.java.language into ceylon.language proper, and create a .ceylon for it. Continue refactoring ArraySequence, SequenceBuilder and SequenceAppender to apply flyweight pattern further, avoiding copies where possible. Change internalSort_.java to use Arrays.sort instead of a java.util.List
Issue #186: Add some JVM tests for SequenceBuilder
Doc typo
Issue #95: Add test for ArraySequence in Ceylon
Issue #209: Add a test
Fix #41 in a non-great way, and add more tests for normalized
ArraySequence inherits Sequence.string
Get rid of the ArraySequence(Element...) constructor, replace it with an ArraySequence.instance(Object[]) factory method