jam is deprecated
jam is deprecated
- Subject: jam is deprecated
- From: Xochitl Lunde <email@hidden>
- Date: Wed, 6 Jan 2010 11:27:04 -0600
I have seen some mailing list threads
that suggest keeping Leopard builds around to be able to use Jam to build
for backward compatibility. I am not sure if I need to or should
do this. My program has a Java GUI which already uses an ant built
on Linux. I wanted Xcode to build me a nice little bundle though,
so on Mac OS 10.5.8 I created a project with a Java Application target
in Xcode 3.0. With little headache, this built me a great litte *.app
bundle that I transplanted to a 32-bit machine running Leopard using Java
1.5. My Java GUI requires 1.6 features, so the first thing the app
does is check which version of JVM launched it and then try to display
a helpful message about why you need Java 1.6 and where you ought to get
it from.
What I read in an earlier thread was
that I need the Leopard build to be able compile for a target JVM of 1.4
or 1.5 so that my program can display a useful message instead of allowing
the command line to throw out a bunch of Java exceptions that don't mean
anything to non-Java-programmers (including me). Did I understand
that correctly?
My colleague only has Snow Leopard,
so he cannot build my Java GUI from the project without converting the
targets. If he converts them, will they still work for me in Leopard?
Are we looking at an unending wellspring of issues with some developers
on Leopard and some developers on Snow Leopard?
Thanks,
Xochitl _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden