I would be interessted to help out on that task.
Any help is appreciated! I started configuring the projects a few days back and have been using Q's NSFoundation4J code for experimentation (te code in the foundation projects is basically just Q's NSFoundation4J, moved into the com.webobjects.foundation package structure). I contacted Q and he told me he has some changes he wants to commit to NSFoundation4J, so I decided to wait for that before carrying on with coding.
The projects are currently on bitbucket but they should probably be moved to github, since most of us are there.
The initial writing of the tests is going to take a lot of grunt work. But JavaFoundation and JavaWebObjects aren't too huge, the most frustrating part will probably be that we'll essentially be writing obsolete code :) But I feel that for the project to succeed, it must be binary compatible with current WO so the switch can be made painlessly by the community.
I've been thinking/talking about this for years, but never went ahead since I've been worried about the legal implications of copying the API. The recent ruling in Oracle v. Google has given me confidence that this could actually succeed.
I'd love some feedback and ideas.
Cheers,
- hugi
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden