Johnny Kewl wrote:
>Where can one download the latest version of the Java Ant Jarbunder?
AFAIK, the one already posted is the latest version. If you're not sure,
you should ask the product's supplier.
>The last article supplies jarbundler-1.9.jar... thats what we using and it
>definitely generates MRJ properties
The com.apple.mrj.application.apple.menu.about.name property is still used,
if it's present, but isn't used if it's not. In its place, one of the
other Info.plist keys is used. But it's only a plist key, not a system
property, so it can't be set from the command-line or programmatically.
Furthermore, you haven't said what versions of Java or Mac OS X you're
targeting. There are significant differences if you go back far enough, so
if you're targeting those you have to consider the age at which an API or
file can be used. This is because things have evolved and changed.
>We are not on Mac... we are simply trying to target the Mac, as well as
>every other platform.
If you never test your code on a Mac, how will you ever know it's correct?
If you believe Write Once Run Anywhere is a statement of fact or a product
guarantee, you are mistaken. It's a marketing slogan. It would be more
accurate as "Write Once Test Everywhere".
If you don't test your code on the target platform, it is very unlikely you
will succeed, especially if you are relying on platform-specific features.
This is true of all platforms, not just Macs.
I would never consider targeting Windows unless I actually tested my app
there, not least because every platform has its own set of bugs, and I'll
never know if I'm hitting any unless I test. Worse, if I were to develop
on a Mac and blindly build a ".exe" file that performed registry access,
and just assumed all the untested code was correct, that would be extremely
naive, even foolish. It would be nice if software development worked like
that, but it doesn't.
You seem to be reinventing a multi-platform installer product, so it might
be simpler if you just used an existing one instead of reinventing it:
<http://en.wikipedia.org/wiki/InstallAnywhere>
<http://install4j.com>
>Every article that we find seems to have a slightly different story....
Things change. What date is the article? What OS & Java version?
>If someone can just point me to the current technical spec for a Mac.App
Not a spec, but this is fairly accurate:
<http://developer.apple.com/documentation/CoreFoundation/Conceptual/CFBundles/Co
ncepts/BundleAnatomy.html>
From this page, read the links that aren't release notes:
<http://developer.apple.com/referencelibrary/API_Fundamentals/Java-fund-date.htm
l>
>When I talk to MACers... the assumption seems to be that its developed,
>deployed and used on a Mac???
No, the assumption is that it's tested on a Mac.
Many developers build on non-Mac platforms, but they realize that testing
their product on the target platform is an important step in delivering
quality. If you don't find your mistakes, your users will.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
