Changed to snapshot version; added maven repository for deployment
Added automatic deployment to sonatype repo with travis
removed the FileBuffer from Nephele, and everything that uses it (Checkpointing, FileChannels)

Changed Nephele MemoryBuffer to wrap PACT MemorySegment instead of java.nio.ByteBuffer

Addressed Stephans comments
new memory segments methods

Remove checkpointing and envelope consumption logic

Signed-off-by: Robert Metzger <metzgerr@web.de>

Removed compression from nephele

Re-added tests.

Re-enabled JobManagerITCase with reduced logging verbosity.
Reduced test logging verbosity to only print warn messages.
Fixed classloader delegation of task conf
Added maven-profiles to enable switching between yarn and non-yarn hadoop
Remove pact-examples dependency in pact-clients.

pact-clients was dependent on pact-examples in order to run
LocalExecuterTest. The problem with that was, that this prevented the
use of the LocalExecuter within the pact-examples module (circular
dependency). Hence the LocalExecuterTest was moved to the pact-test
module and the pact-examples depedency was removed from pact-clients.
First part of fix to exclude pact-hbase when hadoop v1 is used
Added extra profile entries in the pom.xml files in order to fix the hadoop_v1 compilation problems.
Merge pull request #1 from aalexandrov/hadoop-maven-profiles

Fix from Alexander, so that pact-hbase is only included if yarn is used (because it is not compatible with hadoop v1)
Made the hadoop_v1 profile active by default.
Moved hadoop.version property to the profiles.
Update README.md
Update Readme.md with project overview and a little tutorial.
Merge pull request #85 from rmetzger/gith_readme

Update Readme.md with project overview and a little tutorial.
Update README.md
Update README.md
Rename SetId() to setId()
Hopefully fixed a bug in the pact compiler for branching plans:
	- added a test case provided by Anja Kunkel from HU Berlin
	- my understanding of the bug is the following: During a check if additional pipeline breakers are necessary,
	the compiler checks for the LocalStrategy of a SinkJoinerPlan. The SinkJoinerPlan is a "fake" plan element to group multiple output sinks into one sink (the compiler assumes one root node, this is why a "fake" plan node is required).
	The local strategy of SinkJoinerPlan is initialized as NONE, which means that we just pass through the elements (which makes sence since we are talking about a sink) The initialization of a NONE-local strategy assumes only one input, not two.
	I replaced the LocalStrategy with BINARY_NO_OP, which is a NONE for two input.
	The compiler is now able to do its pipline breaker checks.
Merge pull request #2 from aalexandrov/hadoop-maven-profiles

Made the hadoop_v1 maven profile active by default (hadoop version 1.2.1)
Update README.md