Thanks, Guido. I move the WOFrameworks down but it didn't work.
Here is the configuration of my working machine: (without error) http://farm3.static.flickr.com/2299/1812761484_52ff1aba62_o.png And this is another one: (oops! error) http://farm3.static.flickr.com/2003/1811918265_0cef8587bb_o.png You'll notice that the order of WOFrameworks in the latter picture is even lower than the working one. And I tried all possible order permutation. I just wondering if I should revert those generic code to avoid those error... Regards, yllan On 11/1/07, Guido Neitzer <[EMAIL PROTECTED]> wrote: > > On 31.10.2007, at 21:03, Yung-Luen Lan wrote: > > > Recently I update my project with Generic code like > > NSArray<EOSortOrdering>. On my machine, it did not generate error in > > Eclipse 3.2.2 with latest stable WOLips and Wonder 4.0. (Mac OS X > > 10.4.10, Java 1.5.0_07, WebObjects come with Xcode 2.4) > > > > But on another machine, almost the same configuration, Eclipse 3.2.2 > > with latest stable WOLips, Wonder 4.0, Mac OS X 10.4.10, Java > > 1.5.0_07, WebObjects 5.3.3, eclipse whining "The type NSArray is not > > generic; It cannot be parameterized with arguments <EOSortOrdering>" > > and failed to compile. > > > > I couldn't figure out what could make this difference. Did I miss > > something to check? > > Classpath ordering. Check the project properties --> Build path --> > Order and export and move the WOFrameworks waaaaayyy down. > > cug >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
