Add OSGi headers.

Fixed #1.
Test deps conditional on TestKeys.includeTestDependencies
Merge pull request #3 from dragos/issue/osgi-headers

Add OSGi headers and source bundle
Switch to -SNAPSHOT version.
Merge pull request #4 from dragos/issue/snapshot-version

Switch to -SNAPSHOT version.
Make partest version a setting

Note: this fixes the breakage introduced by b9695f013a (could not `test`).
Apparently, the order of the test dependencies matters...
(Perhaps because of the conflicting binary version of xml/parsers?)
Exclude scala-xml from transitive dependencies of partest.

As discovered here:
https://github.com/scala/scala-xml/pull/6#issuecomment-26614894
we would have two different versions of scala-xml on test classpath:

  1. scala-xml classes compiled from source (we are in scala-xml
     project)
  2. scala-xml transitive dependencies of partest

Duplicated classpath entries are always dangerous. I implemented a
set of exclude rules that get rid of transitive dependencies of
scala-xml. This fixes the problem of JUnit using wrong version of
scala-xml for testing (now there's only one choice).

Also, this allowed me to to enable conflictWarning again. They are
very useful to warn us against dangerous situations that almost always
result in broken classpath (as we just learned).
Migrate a few partest jvm tests to JUnit tests.

Migrated to JUnit the following tests (from test/files/jvm):

   * t0632.scala
   * t1118.scala
   * unittest_xml.scala

None of those tests were dependent on anything jvm specific.
Remove test/files/jvm/backendBugUnapply.scala test.

It doesn't seem to test anything XML-specific and I couldn't trace
what kind of backend problem this test is supposed to guard against.
Migrate partest jvm/xmlstuff.scala test to JUnit.
Migrate partest jvm/xmlpull.scala test to JUnit.
Migrate partest jvm/xmlattr.scala test to JUnit.
Migrate partest jvm/xml04embed.scala test to JUnit.
Migrate partest jvm/xml03syntax.scala test to JUnit.
Merge pull request #6 from gkossakowski/master

Migrate majority of partest jvm tests to JUnit
Do not include partest and it's dependencies in generated pom.

Define custom Ivy configuration that contains all dependencies of
partest (and partest itself) and make sure that this configuration
is not considered when pom is generated.

Remove the comment about significance of dependency order declaration.
Given the fact that we excluded conflicting, transitive dependencies
and all partest dependencies are isolated from regular dependencies
the situation is much better.
Merge pull request #7 from gkossakowski/partest-deps

Do not include partest and it's dependencies in generated pom.
Revert "Do not include partest and it's dependencies in generated pom."

This reverts commit 053193f83a2e84996ac33e692322ea5b0b3e1321.

I misunderstood bevaior of test scope/configuration in relation to
transitive dependency. Partest can be included in generated pom as
long as it's declared to be in test scope. Therefore the changes
in 053193f83a2e84996ac33e692322ea5b0b3e1321 are not needed.
Merge pull request #9 from gkossakowski/revert-partest-deps

Revert "Do not include partest and it's dependencies in generated pom."
Upgrade to Scala 2.11.0-M6.

That entails tweaking dependencies once again. Hold your breath:

  * we can't upgrade to new version of partest because it's not been
    released yet; we can't release it first because scalacheck is needed
  * therefore we are using the M5 version and then we have to exclude
    all transitive dependencies that were built against M5; one such
    dependency would be scala-compiler itself
  * since we excluded all transitive dependencies we need to bring some
    back: we add diffutils and scala-compiler but M6 version

All newly added dependencies are in "test" scope. I verified that nothing
leaks to a pom.xml.

Also, updated check file for one of the tests because there were some
improvements to error handling that changed errors being emitted. See
SI-7895 for details.