command line options in PB OSX?
command line options in PB OSX?
- Subject: command line options in PB OSX?
- From: Jonathan Rochkind <email@hidden>
- Date: Thu, 22 Jan 2004 14:02:54 -0600
I am using ProjectBuilder with OSX 10.2.8 WO 5.2.1 (and based on
recent messages, I'm glad I haven't upgraded to Panther/5.2.2 yet!)
How do I set command line options for a WO app I'm launching from PB?
The only way I can figure out is in Targets/[Main
target]/Settings/Expert View/, the "JVM_OPTIONS" variable. The
problem with this is that the setting ends up in the
UNIXClassPath.txt (etc) files, which are kind of a fixed attribute of
the app as a whole, so when I deploy the built app, these command
line arguments will still be used. I want one set of command line
arguments for development, and another when I actually deploy the app.
Back on Windows PB, the command line arguments (set with the
'checkbox' icon in the 'run' panel) were only saved in my personal PB
preferences, and did not become a fundamental attribute of the
project as a whole. So I could set command line arguments in
development, and when I deployed the project, they woudln't be there,
they'd be gone. Which is just what I want.
There's no way to do this on PB OSX? I can't figure one out. This
would be a serious inconvenience. (This, and others, are making me
wonder why I switched from Windows development to OSX dev
environment. At least I was used to the problems and idiosyncracies
in the Windows dev tools, and had worked out how to work under the
constraints it imposed. Oh well, I'm committed now, hardware has been
bought, we're an OSX shop now. I had expected this would be a
pleasant change. doh.)
--Jonathan
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.