To view parent comment, click here.
To read all comments associated with this story, please click here.
I couldn't find anything in the Harmony-project SVN which made me think this came from there.
Not in incubator either.
So the license at the top is a mistake, atleast.
Maybe someone ran a tool to place such a license at the top of files which didn't have anything yet...?
The code from Google and Oracle/Sun looks very similar, their is definitely a common origin. The quesion obviously is, what is the origin. It could have been generated based on some specification for the x509-certificate that this deals with.
But the creator (or person that imported the source into the Android git repository) should be able to point out where it came from.
Or completely the other way around, there might be a test-suite which tried to use this API and they created a similair API because it was needed to pass some tests.
Edited 2010-10-28 23:35 UTC
Maybe the API-documentation was the source for Android from which they derived the function list and the source for the API-documentation was the source from Oracle/Sun.
Maybe that is allowed by the copyright law, I don't know.
Although, I have to say, I can't find a API-document that proves this.
Edited 2010-10-28 23:44 UTC




Member since:
2008-08-19
Absolutely - everything about those comparisons screams "decompiler". All the names that would appear in the bytecode (class name, field names) are identical; all local variables have been given obviously machine-assigned names based on their type (set1, flag1, etc).
Looks awfully damning... if this code really came from Harmony, the Apache guys have been *really* careless about the code they accept.