update dematerialize so can chain correctly

[prabirshrestha]

Just noticed this when I actually had to chain it.

Observable<File> saveResult = ....;

current:

Observable<Notification<File>> a = saveResult.materialize().dematerialize();

expected:

Observable<File> a = saveResult.materialize().dematerialize();

here is what is happening

Observable<File> x = saveResult;
Observable<Notification<File>> y = x.materialize();
Observable<Notification<File>> currentResult = y.dematerialize();
Observable<File> expectedResult = Observable.dematerialize(y);

workaround is to use static method to get the expected result.

With this change you can chain correctly. Added unit test.

Observable<Integer> obs = Observable.just(1);
Observable<Integer> chained = obs.materialize().dematerialize();

This will be a breaking change. But I think this is the expected way.

[cloudbees-pull-request-builder]

RxJava-pull-requests #29 SUCCESS
This pull request looks good

[benjchristensen]

So it's just the generics that are wrong?

[benjchristensen]

Yeah ... this works without this fix:

Observable chained = obs.materialize().dematerialize();

but the compiler doesn't like this because the generics are wrong:

Observable<Integer> chained = obs.materialize().dematerialize();

[benjchristensen]

Released in 0.6.1 https://github.com/Netflix/RxJava/blob/master/CHANGES.md#version-061-maven-central

[prabirshrestha]

awesome. thanks. now need to wait for the maven repo update :(

I did notice the Gradle Release Plugin - pre tag commit: 'rxjava-0.6.1'. 671db35

is the jar in maven and ci the same?

[benjchristensen]

The jar is built by internal Netflix build servers and then uploaded to Maven Central.

The public CI (CloudBees) also builds the jar but that one never goes anywhere.