a) Leopard deprecated the Java-ObjC bridge support making the
legacy tools fail to function properly without this support being
reimplemented somehow.
b) The legacy tools were well overdue for a rewrite
c) Eclipse + WOLips had gained substantial traction internally and
within the WO community and had reached the point of being a viable
replacement.
d) Xcode was never going to compare with Eclipse as a Java IDE.
I have a slightly different take on item d). While I agree exactly
with the statement, I think it important to point out that Xcode is a
really great IDE. Just not a great Java IDE. I use Xcode for Cocoa/
Objective-C development and it is by far my favorite IDE to use. It
was not, and will likely never be a great Java IDE.
Transitioning WO development to Eclipse (a true Java IDE) I'm sure
has now freed Apple to focus Xcode on Cocoa/Carbon development (C
based development). And this focus has gone a long way to allow key
improvements to their Macintosh software development tools.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
