Way too funny. But, then again, a good depate on these kinds of issues is a splendid way to waste time.
Skip -----Original Message----- From: BJ Freeman [mailto:[EMAIL PROTECTED] Sent: Monday, November 19, 2007 12:03 PM To: dev@ofbiz.apache.org Subject: Re: well so much for backward compatibility. (RANT) I apologize for causing such a ruckus First of all I had a long day before doing this. So it did not dawn on me that the errors were normal. that instead of dropping framework from the trunk into my ver 4.0 I should drop my application into the current trunks. as I said below, I tried using 1.4 compiler on code the includes 1.5 additions. the 1.4 compiler is just not able to evaluate 1.5 syntax. BJ Freeman sent the following on 11/19/2007 12:10 AM: > Well I guess I am not fair. > I pulled the framework into Ver 4.0 which is compiling using 1.4. > So I guess even though I don't use the 1.5 stuff, it will error. > and since the 1.4 compiler is not able to evaluate 1.5 > I am getting errors. > ServiceUtil.returnError-> method returnError(string) is not defined. > UtilXml.childElementList-> childElementList(list) in UtilXml is not > applicable for agurments (element, string) > are a couple. > > > > David E Jones sent the following on 11/18/2007 11:52 PM: >> Could you be more specific, ie what is broken and what errors are you >> getting? >> >> -David >> >> >> On Nov 19, 2007, at 12:45 AM, BJ Freeman wrote: >> >>> I just plugged my code from ver 4.0 into trunk >>> guess what >>> none of it works. >>> so what happend to depreciating then removing, based on releases. >>> Sure ver 1.5 has lots of neat things. >>> but shouldn't we try to conserve as much of the programming effort as we >>> can. >>> Why not add the same functions and method and leave the 1.4 compatibility > > >
