Example code:

[code]
static public void main(String args[]) {
println( "in main" );
PApplet.main(new String[] { "<sketch_name>" } );
}


void setup(){
println( "in setup" );
}
[/code]


When run from the PDE this outputs just
"in setup"

When run as an exported application it results in
"in main"
"in setup"


Be it a bug or a feature request, I think it is a bit incosistent.
The problem seems to be in Runner.java#getSketchParams():
[code]
[...]
params.add("processing.core.PApplet");
[...]
params.add(appletClassName);
[/code]

If the occurence of "processing.core.PApplet" was replaced by appletClassName it should work.

p.s. priority superlow... just came across it and thought it might be interresting.

Interesting, this is a leftover from when sketches were run in the same
process (pre-1.0) so that they'd be faster. But now that we're launching
out to other code, we may as well handle the main() in the same fashion.
Might actually reduce some code to fix it.

k, the other reason for this is that the main() that's written at runtime
adds some options to tell the sketch to talk to the editor. (e.g. the
editor window location will be forgotten).

buuut.. if you're gonna overwrite main(), then we may as well let you break
your code. so i've made the change to simply run the main as provided, if
the user has created their own.