On 2009-09-01, at 5:14 PM, Clark Mueller wrote:
Yep, there is definitely that risk... A good practice might be to
have a QA box set up that matches your deployment software
configuration (say 10.5.8 and 1.5.x), and run the build that you are
going to test and deploy using that box. That can help mitigate a
lot of that risk.
Yeah, we were thinking of setting up a Hudson build server anyway. So
we can probably dedicate a box to do that and be a QA box.
The best practice would of course be to match your development JDK
and OS to your deployment JDK and OS, if it's practical to do so.
Oh, come on, where is the fun in that? :-)
Clark
On Sep 1, 2009, at 2:03 PM, Mike Schrag wrote:
But doesn't that still compile using the 1.6 SDK since Snow
Leopard doesn't have 1.5? Or is Java 1.6 able to compile to a 1.5
compatible byte code representation?
Yeah, javac and Eclipse's compiler can both generate 1.5 compatible
binaries. I suspect it can't tell if you use 1.6 _API_, but it
won't let you use 1.6 source features.
ms
;david
--
David LeBer
Codeferous Software
'co-def-er-ous' adj. Literally 'code-bearing'
site: http://codeferous.com
blog: http://davidleber.net
profile: http://www.linkedin.com/in/davidleber
twitter: http://twitter.com/rebeld
--
Toronto Area Cocoa / WebObjects developers group:
http://tacow.org
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [email protected]
