SI-6701 add SYNTHETIC flag to the reflection api
SI-7304 improve deprecation warnings for tree factory methods
SI-6489 parsing in macros should provide proper positions

1. macro parsing doesn't use toolbox any more but calls parser directly

2. in order for this to work parser has to be refactored to limit
   usage of currentUnit and rewire it into parser's local unit
   method which might use currentUnit for some parsers but will
   user proper unit for UnitParser

3. similar change has to be done to make compilation unit's
   reporter overridable
refactor variable arity definitions

Transform current arrays of symbols into function-like objects
that return NoSymbol at all places where corresponding arity isn't
available.
Remove build.number.maven

I can't find any justification for having this information
in both build.number and build.number.maven.

They have drifted apart on the 2.10.x branch, although that
doesn't matter because build.number is correct, and loaded first,
and Ant properties are write-once.

I'm assuming that the Ant tasks in src/build/pack.xml are only
invoked through the <antcall>-s in ./build.xml.

Here's a test of that from the 2.10.x branch:

	% cat build.number
	#Tue Sep 11 19:21:09 CEST 2007
	version.major=2
	version.minor=10
	version.patch=3
	# This is the -N part of a version.  if it's 0, it's dropped from maven versions.
	version.bnum=0

	# Note: To build a release run ant with -Dbuild.release=true
	# To build an RC, run ant with -Dmaven.version.suffix=-RCN

	% cat build.number.maven
	version.major=2
	version.minor=10
	version.patch=0

	% git diff
	diff --git a/build.xml b/build.xml
	index 3a83aa4..5cb952c 100644
	--- a/build.xml
	+++ b/build.xml
	@@ -62,6 +62,9 @@ TODO:
	   <target name="distpack" depends="dist.done, docs.done">
	     <ant antfile="${src.dir}/build/pack.xml" target="pack-all.done" inheritall="yes" inh

	+  <target name="distpack.maven.info">
	+    <ant antfile="${src.dir}/build/pack.xml" target="pack-maven.info" inheritall="yes" i
	+
	   <target name="distpack-maven" depends="dist.done, docs.done">
	     <ant antfile="${src.dir}/build/pack.xml" target="pack-maven.done" inheritall="yes" i

	diff --git a/src/build/pack.xml b/src/build/pack.xml
	index 20c4034..56863ff 100644
	--- a/src/build/pack.xml
	+++ b/src/build/pack.xml
	@@ -133,6 +133,10 @@ MAIN DISTRIBUTION PACKAGING
	     <mkdir dir="${dists.dir}/maven/${version.number}"/>
	   </target>

	+  <target name="pack-maven.info">
	+    <echo message="version.patch = ${version.patch}"/>
	+  </target>
	+
	   <target name="pack-maven.libs" depends="pack-maven.start">
	     <macrodef name="mvn-copy-lib">
	       <attribute name="mvn.artifact.name"/>

	% ant distpack.maven.info
	Buildfile: /Users/jason/code/scala2/build.xml

	distpack.maven.info:

	pack-maven.info:
	     [echo] version.patch = 3

Notice how the stale `version.patch=0` in build.number.maven is
ignored.
SI-7844 Intellij setup.sh is not working for Ubuntu 12.04

Added "-f" option to the command "rm"
Merge pull request #2946 from jinfu-leng/ticket/7844

SI-7844 Intellij setup.sh is not working for Ubuntu 12.04
SI-7841 Remove commented out AnyRef specialization from Function{0,1}.

In a sign of decreased optimism about that facility.
SI-7845 Disable test for JSR 233

For Paul, it steals focus when it runs.

For me, it fails with some platform specific extra output:

-ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory could not be instantiated: java.lang.UnsatisfiedLinkError: no AppleScriptEngine in java.library.path
 n: Object = 10
 12345678910

So off to the holding pen for now.
Merge pull request #2948 from retronym/ticket/7845

SI-7845 Disable test for JSR 233
Merge pull request #2935 from densh/topic/si-7304-6489-6701

SI-6701, SI-7304, SI-6489, variable arity definitions refactoring
SI-7847 Static forwarders for case apply/unapply

These were excluded in f901816b3f because at the time they
were compiler fiction and translated to calls to the case
class constructor or accessors.

But since they are now bona-fide methods (albeit still occasionally
bypassed as an optimization), we can expose them conveniently to our
Java brethren.

The cut-and-pastiness of GenBCode starts to hinder maintenance.
Here's a report of further duplication that we have to fix up
post haste: https://gist.github.com/retronym/6334389
SI-7841 Remove AnyRef specialization from AbstractPartialFunction

This was missed in cc3badae1

Compatibility classes for formerly specialized variants used
by Scalacheck have been added as a stopgap measure until we
publish the next milestone.
SI-7841 More robust unspecialization of names

Names like `T1$sp`, which can arise from `AnyRef` specialization,
were leading to negative length Names if they ever passed through
`unspecializedName` or `splitSpecializedName`. This code path was
touched when printing the tree of a certain AnyRef specialized
classes after specialization, such as `AbstractPartialFunction`
(which had such specialization until a few commits ago.)

This commit handles that case correctly, and generally hardens
against unexpected names, which could pop up from third party
classes.

The documentation for `splitSpecializedName` transposed the
class and method specializations. The things you discover
when you turn examples in documentation in to test cases!

In addition, we now require non-negative length and offset in
`newTermName`
Fix typo in documentation.
Merge pull request #2950 from retronym/ticket/7841

Damage control related to AnyRef specialization
Merge pull request #2951 from retronym/ticket/7847

SI-7847 Static forwarders for case apply/unapply
SI-7852 Test to show the status quo bytecode for "" == ...

Will be somewhat leaner after the next commit.
SI-7852 Omit null check for "".==

Although the same the code would be later optimized by -Yconst-opt,
we can offer the same lean byte code to those compiling without that
option by being more discerning when translating ==.

This helps people using bytecode based code coverage tools
such as jacoco that would emit "branch not covered" warnings
for the impossible null check.
SI-7852 Test to show status quo of for SomeModule.==

For which we can also elide the null check, and will in the
next commit.